Hello There:
I don’t know whether this is feasible or not, but I was wondering if
there was a way to set the ticket ownership to default the name of the
user who is currently logged in instead of nobody? So far whenever I
create a ticket I ALWAYS have to change the owner to my name.
Thanks for your reply,
Serge
You can write a scrip that sets the owner to the logged
in user when a ticket is created through the web interace.
-ToddOn Tue, Aug 10, 2004 at 09:11:00AM -0400, Serge Bianda wrote:
Hello There:
I don’t know whether this is feasible or not, but I was wondering if
there was a way to set the ticket ownership to default the name of the
user who is currently logged in instead of nobody? So far whenever I
create a ticket I ALWAYS have to change the owner to my name.Thanks for your reply,
Serge
Be sure to check out the RT wiki at http://wiki.bestpractical.com
Here’s a scrip which change the ticket owner to admincc. You can easily
customize it for your needs.
Condition: OnCreate
Action: UserDefined
Custom action preparation code: return 1;
Custom action cleanup code:
if (defined($self->TicketObj->QueueObj->AdminCc->MembersObj->Next))
{
$self->TicketObj->SetOwner(
$self->TicketObj->QueueObj->AdminCc->MembersObj->Next->MemberId);
}
return 1;
Stage: TransactionCreate
Template: Global Template Blank
-Dimitry-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Serge Bianda
Sent: Tuesday, August 10, 2004 6:11 AM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Ticket Ownership
Hello There:
I don’t know whether this is feasible or not, but I was wondering if there
was a way to set the ticket ownership to default the name of the user who is
currently logged in instead of nobody? So far whenever I create a ticket I
ALWAYS have to change the owner to my name.
Thanks for your reply,
Serge
I don’t know whether this is feasible or not, but I was
wondering if there was a way to set the ticket ownership to
default the name of the user who is currently logged in
instead of nobody? So far whenever I create a ticket I ALWAYS
have to change the owner to my name.
Using 3.0.10:
/opt/rt3/share/html/Ticket/Create.html
< <& /Elements/SelectOwner, Name => “Owner”, QueueObj => $QueueObj, Default
=> $ARGS{Owner} || $session{CurrentUser}->Id || undef &>
<& /Elements/SelectOwner, Name => “Owner”, QueueObj => $QueueObj, Default
=> $ARGS{Owner}||undef &>
-matt
Matthew Hanley
mhanley@cxtec.com
Thanks Matt, this worked just fine. I didn’t need to create a scrip
anymore.
SergeFrom: Matt Hanley [mailto:MHanley@cxtec.com]
Sent: Tuesday, August 10, 2004 2:07 PM
To: Serge Bianda; rt-users@lists.bestpractical.com
Subject: RE: [rt-users] Ticket Ownership
I don’t know whether this is feasible or not, but I was
wondering if there was a way to set the ticket ownership to
default the name of the user who is currently logged in
instead of nobody? So far whenever I create a ticket I ALWAYS
have to change the owner to my name.
Using 3.0.10:
/opt/rt3/share/html/Ticket/Create.html
< <& /Elements/SelectOwner, Name => “Owner”, QueueObj => $QueueObj,
Default
=> $ARGS{Owner} || $session{CurrentUser}->Id || undef &>
<& /Elements/SelectOwner, Name => “Owner”, QueueObj => $QueueObj,
Default
=> $ARGS{Owner}||undef &>
-matt
Matthew Hanley
mhanley@cxtec.com
Before I go re-inventing the wheel…
Has anyone looked at adding more specific datatypes for custom fields
than “select from a list” and “enter text?” Specifically I’m thinking
things like currency values, dates, regex matches…
-n
------------------------------------------------------------memory@blank.org
five claws each rear paw
seven claws on the front paws
a cat named Haiku (–Mark Amidon)
http://blank.org/memory/----------------------------------------------------
Before I go re-inventing the wheel…
Has anyone looked at adding more specific datatypes for custom fields
than “select from a list” and “enter text?” Specifically I’m thinking
things like currency values, dates, regex matches…
Yes. And we’ve implemented it in the RT 3.3 branch. We just haven’t
exposed UI for setting up the validation.
In the immortal words of Jesse Vincent (jesse@bestpractical.com):> On Tue, Aug 10, 2004 at 05:09:23PM -0400, Nathan J. Mehl wrote:
Before I go re-inventing the wheel…
Has anyone looked at adding more specific datatypes for custom fields
than “select from a list” and “enter text?” Specifically I’m thinking
things like currency values, dates, regex matches…Yes. And we’ve implemented it in the RT 3.3 branch. We just haven’t
exposed UI for setting up the validation.
Woohoo!
When does 3.3 close for new features? 
-n
------------------------------------------------------memory@blank.org
“As long as Nixon was politically alive, we could always be sure of
finding the enemy on the Low Road. There was no need to look anywhere
else for the evil bastard.” (–Hunter S. Thompson)
http://blank.org/memory/----------------------------------------------
Yes. And we’ve implemented it in the RT 3.3 branch. We just haven’t
exposed UI for setting up the validation.Woohoo!
When does 3.3 close for new features?
The schema’s settled. The API’s mostly settled. But really what’s
missing right now is just UI for editing the validation code.
Has anyone looked at adding more specific datatypes for custom fields
than “select from a list” and “enter text?” Specifically I’m thinking
things like currency values, dates, regex matches…
Yes. And we’ve implemented it in the RT 3.3 branch. We just haven’t
exposed UI for setting up the validation.
Any other new features for custom fields?
I’d really like to see better support for adding new values on the fly
for a select list (Movable Type do this well with their Categories), and
a default sort order - it’s really painful to have to enter a sort order
for every entry, when I just want the list to be sorted
alphabetically…
Of course, now someone can point out ways to do both of these at the
minute …
Tony