I would like for unprivileged users to be able to enter and view custom
fields on the tickets they enter.
I setup the custom field for Ticket and added it to a specific Queue. I
figured out how unprivileged users can enter custom fields for tickets
they file -- SeeCustomField and ModifyCustom
Hi All,
I'm trying to reach a requirement that we want one global custom field,
which is using external values that populated with some REST API, to has
different drop-down list filtered by Queue name. Is this possible to config
in /lib/RT/CustomFieldValues/xx.pm file? Or is there any other way to
I tried googling and found an unanswered email to this list from 2006.
I also found a bunch of links relating to RT's Lifecycle functionality, but
I wasn't able to figure out if there was a built in way for RT to
auto-resolve/reject/(some other status) tickets that have been stalled for
a period o
On Tue, Aug 4, 2015 at 1:41 PM, Mike Johnson wrote:
> I tried googling and found an unanswered email to this list from 2006.
>
> I also found a bunch of links relating to RT's Lifecycle functionality, but
> I wasn't able to figure out if there was a built in way for RT to
> auto-resolve/reject/(so
I would like to pre-populate the description of a new ticket. For
example, if I filed a bug on Red Hat's Bugzilla, a new bug description
already contains the text:
Component:
Version:
Problem:
Expected Results:
Actual Results:
Additional Info:
A feature like this would be very helpful to guidi
On Tue, Aug 4, 2015 at 2:57 PM, Joseph D. Wagner
wrote:
> I would like to pre-populate the description of a new ticket. For example,
> if I filed a bug on Red Hat's Bugzilla, a new bug description already
> contains the text:
>
> Component:
> Version:
> Problem:
> Expected Results:
> Actual Resul
Hi All, hope some one can give me some insight to below or refer to a UTL
Currently I am using RT as below (must be the must be the simplest way of
using).
1. I have created a queue per each customer
2. and Create, admincc etc the customer and some internal supervisors
3. Each queue has its own