On Tue, Mar 7, 2017 at 3:16 AM, Woody - Wild Thing Safaris
wrote:
> I added "Users" to line 2016 in CustomField.pm
>
> return 0 unless $self->LookupType =~ /RT::(?:Ticket|Transaction|User)$/;
>
> and it seems to behave as expected. But RT::Users must have been left out
> for a reason?
Possibl
I added "Users" to line 2016 in CustomField.pm
return 0 unless $self->LookupType =~
/RT::(?:Ticket|Transaction|User)$/;
and it seems to behave as expected. But RT::Users must have been left
out for a reason?
w.
On 03/03/17 10:46, Woody - Wild Thing Safaris wrote:
sorry, 4.4.0
On 02
sorry, 4.4.0
On 02/03/17 23:44, Matt Zagrabelny wrote:
What version of RT are you using?
-m
On Thu, Mar 2, 2017 at 1:46 PM, Woody - Wild Thing Safaris
wrote:
Hi RT Folks,
Am i missing something? I see no option to select a "default value" for
"select one value" type custom fields if they a
What version of RT are you using?
-m
On Thu, Mar 2, 2017 at 1:46 PM, Woody - Wild Thing Safaris
wrote:
> Hi RT Folks,
>
> Am i missing something? I see no option to select a "default value" for
> "select one value" type custom fields if they are of lookuptype RT::User?
>
> i tested and if it's R
Hi RT Folks,
Am i missing something? I see no option to select a "default value" for
"select one value" type custom fields if they are of lookuptype RT::User?
i tested and if it's RT::Ticket - default appears, but RT::User - that
input field has disappeared?
w.
--
---
Ken Crocker wrote:
Matthew,
Try creating a scrip that has the condition of "OnCreate", an action
as "user-Defined" and put code in the prep action code area that sets
the CF to the value you want (see below). Put "return 1;" in the
clean-up action area. That should do it.
Prep Action cod
Matthew,
Try creating a scrip that has the condition of "OnCreate", an action
as "user-Defined" and put code in the prep action code area that sets
the CF to the value you want (see below). Put "return 1;" in the
clean-up action area. That should do it.
Prep Action code:
# set the CF Work
I may be being thick here, but I can't see a way to do this from the web
interface. If I create a custom field of 'Select One Value' type, is
there any way of making one of the values selected by default? The
actual application I'm looking at here is for tracking time spent
working on tickets o
Tommie,
Sure. Here is an example of a templete we use for when a ticket is
created. It includes the data from a ticket CF ('Description'). Hope
this helps.
Subject: Request Titled: "{$Ticket->Subject}" has been created!
-
Kenneth Crocker wrote:
> Tommie,
>
>
> You could create several CF's for a ticket; one for each question
> you want to ask. Since tickets live in queues, you can set up
> different CF's for the tickets in a queue. Then, when the help desk
> person looks at the ticket or opens the ticket, the
Tommie,
You could create several CF's for a ticket; one for each question you
want to ask. Since tickets live in queues, you can set up different CF's
for the tickets in a queue. Then, when the help desk person looks at the
ticket or opens the ticket, they can modify the CF with an
an
Dear,
is it possible to set the description field to a default value when you
use "Create ticket in queue".
E.g. we want to fill up the description field with some default
questions our help desk person will ask the requester on phone. He then
fills in the answer after the question.
Can yo
At Monday 9/24/2007 02:43 PM, Mathew Snyder wrote:
I was wondering about that. The code that Kenneth provided as an example uses
LoadByName instead of LoadByNameAndQueue. That fixed it. Thanks.
Mathew
Good - from looking at the (3.4.2) code, LoadByName is just a synonym
for LoadByNameAndQu
I was wondering about that. The code that Kenneth provided as an example uses
LoadByName instead of LoadByNameAndQueue. That fixed it. Thanks.
Mathew
Keep up with me and what I'm up to: http://theillien.blogspot.com
Stephen Turner wrote:
>
> At Monday 9/24/2007 11:26 AM, you wrote:
>> Figure
Mathew,
I think I know why. In your scrip code, you define your "$CFObj" using
"CurrentUser" and "$QueueObj" (See line below).
my $CFObj = RT::CustomField->new( $QueueObj->CurrentUser );
I update our global field for ALL E_mail creates (in a global scrip)
with the ticket subject line (thi
Mathew,
I think I know why. In your scrip code, you define your $CFObj using
current user See line below).
my $CFObj = RT::CustomField->new( $QueueObj->CurrentUser );
I update our global field for ALL E_mail creates with the ticket
subject line (this is so I ALWAYS get some sort of descri
Do you have global modify rights to custom fields or are they set on a
queue by queue basis?
Mathew Snyder wrote:
> What is even stranger is that when looking at the custom fields for each
> queue,
> this particular CF shows up as global. However, I wasn't able to modify it
> via
> my scrip unt
What is even stranger is that when looking at the custom fields for each queue,
this particular CF shows up as global. However, I wasn't able to modify it via
my scrip until I did explicitly apply it.
Keep up with me and what I'm up to: http://theillien.blogspot.com
Kenneth Crocker wrote:
> Mat
Mathew,
That does seem strange. I have only about 25 custom fields and only one
is global. It is not applied to ANY queue and the groups rights are set
so everyone can see it but only privileged can modify it. All others are
applied on a queue-by-queue basis with the group rights set as need
Figured it out. Seems that despite a CF being created as a Global, it has to be
explicitly applied to a queue...strange.
Keep up with me and what I'm up to: http://theillien.blogspot.com
Mathew Snyder wrote:
> I have one DV that I set to a default value whenever a ticket is created.
> I've
>
I have one DV that I set to a default value whenever a ticket is created. I've
tried to port this over to another queue with a different CF/value but it
doesn't seem to work. Here's the code:
my $CFName = 'Environment';
my $DefaultValue = 'default_value';
my $RecTransaction = 1;
my $QueueObj = $
21 matches
Mail list logo
