An idea for RT

Jesse, list,

I was thinking that it might be a really kool option to allow each RT 

installation to configure how all dates are displayed. Not everyone
wants the time info and we all know that not everyone uses the same
format, either “mm/dd/yyyy” or “MMM dayofweek YYYY”, etc. If RT could
allow us to configure it to default all date displays/search results, it
might make it’s visability more user-friendly. Just a thought.

Kenn
LBNL

Jesse, list,

I was thinking that it might be a really kool option to allow each
RT installation to configure how all dates are displayed. Not everyone
wants the time info and we all know that not everyone uses the same
format, either “mm/dd/yyyy” or “MMM dayofweek YYYY”, etc. If RT could
allow us to configure it to default all date displays/search results, it
might make it’s visability more user-friendly. Just a thought.

You haven’t upgraded to RT 3.8 yet, have you? :slight_smile:

You probably already know that limited a choice of formats is available
in 3.8

Under User Preferences, Date and Time Format.

I’m seeing:

  1. Tue Dec 25 21:59:12 1995
  2. Tue, 25 Dec 1995 21:59:12 -0300
  3. 1995-11-24 21:59:12
  4. 1995-1125T21:5912Z

So perhaps there already is way to add more formats.

From RT_Config.pm:

=item C<$DateTimeFormat>

You can choose date and time format. See "Output formatters"
section in perldoc F<lib/RT/Date.pm> for more options. This option can
be overridden by users in their preferences.
Some examples:

C<Set($DateTimeFormat, { Format => ‘ISO’, Seconds => 0 });>
C<Set($DateTimeFormat, ‘RFC2822’);>
C<Set($DateTimeFormat, { Format => ‘RFC2822’, Seconds => 0, DayOfWeek =>
0 });>

=cut

Set($DateTimeFormat, ‘DefaultFormat’);

BrianOn Fri, 2008-07-25 at 11:45 -0700, Kenneth Crocker wrote:

Jesse, list,

I was thinking that it might be a really kool option to allow each RT
installation to configure how all dates are displayed. Not everyone
wants the time info and we all know that not everyone uses the same
format, either “mm/dd/yyyy” or “MMM dayofweek YYYY”, etc. If RT could
allow us to configure it to default all date displays/search results, it
might make it’s visability more user-friendly. Just a thought.

Kenn
LBNL


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Jesse,

HA! No. I've been spending my time looking into using SVK as our 

version control system and getting RT to automatically execute it when a
ticket is opened/resolved. We’re a bit short staffed (like duh, aren’t
we ALL?). That is the plan though. Probably around November. That way I
get to see your smiling face in San Francisco first and pick up any
helpful hints before I stumble through it. I’m REALLY looking forward to
that. OOPPSS! I shouldn’t have given you a warning. he he.

Kenn
LBNLOn 7/25/2008 11:48 AM, Jesse Vincent wrote:

On Fri, Jul 25, 2008 at 11:45:07AM -0700, Kenneth Crocker wrote:

Jesse, list,

I was thinking that it might be a really kool option to allow each
RT installation to configure how all dates are displayed. Not everyone
wants the time info and we all know that not everyone uses the same
format, either “mm/dd/yyyy” or “MMM dayofweek YYYY”, etc. If RT could
allow us to configure it to default all date displays/search results, it
might make it’s visability more user-friendly. Just a thought.

You haven’t upgraded to RT 3.8 yet, have you? :slight_smile:

Kenn
LBNL

Hello All,

As users send tickets via e-mail their tickets are Requester set to
username@email.com but at login they are username and as username cannot see
their e-mailed tickets within the RT website. Is there a way to set it so
logging in users can see their e-mailed tickets? A scrip or config? I just was
moved to running our RT so I’m still fishing through the config’s and setup.

Thanks,

Jorge

Do their usernames have the proper email address? Or do you end up with
2 accounts per person? If the account a user logs in with is not the
same as the account created when the email is sent in, then the user
won’t be able to see the tickets from the other account because you will
have essentially two accounts.

Jorge Aldana wrote:

Well users login with username and the ticket is sent in via e-mail as
username@email.com so yes there’s two accounts.

Does RT allow for users to login via username@email.com? Or is there a scrip to
alter the tickets to set it to username instead of username@email.com as
requester when tickets are created? Or force users to login as
username@email.com?

I’m still fishing through the doc’s and learning RT so don’t quite know where
the tweaking can take place for this. Any guide or pointing to guides if anyone
can.

Thanks,

JorgeOn Mon, 28 Jul 2008, John Arends wrote:

Do their usernames have the proper email address? Or do you end up with
2 accounts per person? If the account a user logs in with is not the
same as the account created when the email is sent in, then the user
won’t be able to see the tickets from the other account because you will
have essentially two accounts.

Jorge Aldana wrote:

Hello All,

As users send tickets via e-mail their tickets are Requester set to
username@email.com but at login they are username and as username cannot see
their e-mailed tickets within the RT website. Is there a way to set it so
logging in users can see their e-mailed tickets? A scrip or config? I just was
moved to running our RT so I’m still fishing through the config’s and setup.

Thanks,

Jorge


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

In RT 3.6.0 it doesn’t seem to create 2 accounts for this.

Thank you,
Micah Gersten
onShore Networks
Internal Developer

Jorge Aldana wrote:

The fact that you have two accounts is the problem. An account can have
a username and an email address so they can log in as ‘bob’ but have an
email address of bob@organization.com

I’m not sure how you’d fix this problem other than consolidating down to
one account per person. There isn’t a way that I’m aware of to say
"these 2 users are really the same person."

Jorge Aldana wrote:

Try RT::Extension::MergeUsers (unless that has been merged into 3.8?)
from CPAN.

John Arends wrote:

The fact that you have two accounts is the problem. An account can have
a username and an email address so they can log in as ‘bob’ but have an
email address of bob@organization.com

I’m not sure how you’d fix this problem other than consolidating down to
one account per person. There isn’t a way that I’m aware of to say
"these 2 users are really the same person."

Jorge Aldana wrote:

Well users login with username and the ticket is sent in via e-mail as
username@email.com so yes there’s two accounts.

Does RT allow for users to login via username@email.com? Or is there a scrip to
alter the tickets to set it to username instead of username@email.com as
requester when tickets are created? Or force users to login as
username@email.com?

I’m still fishing through the doc’s and learning RT so don’t quite know where
the tweaking can take place for this. Any guide or pointing to guides if anyone
can.


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Drew Barnes
Applications Analyst
Network Resources Department
Raymond Walters College
University of Cincinnati