The rights work like this:
SeeCustomField - allows the members of the group given this right to
actually see the ticket field and it’s current value in the ticket display
(regardless of the Queue).
ModifyCustomField - allows the members of the group given this right to
actually “modify” the value in that field for a ticket (regardless of the
AdminCustomField - allows the members of the group given this right to
create, delete, define the name, description, set mandatory value and
possible “select” values for others to select from in a ticket (regardless
of the Queue).
AssignCustomFields - allows the members of the group given this right to
"apply" or “allow” a Custom Field to be available for tickets in a Queue.
Granting the 1st 3 rights has no effect on seeing/modifying these custom
fields in a ticket if the CF hasn’t been applied to a particular Queue.
These rights were originally set up to be given at the Group level only.
When configuring a Queue, you wouldn’t see rights to see or modify a Custom
Field. This is still the general practice as it allows for LESS maintenance
on CF rights. An example:
If I have 20 Queues and Group “A” has various rights to 5 of them. I grant
the rights I want them to have and then whatever Queue has that CF applied
to it AND Group “A” has rights to that Queue, then I don’t have to go into
each Queue and grant those rights.
On the other hand, I NOW (due to later versions) CAN grant those rights at
the Queue level for another group that I DO NOT want to have access in the
other Queues, but DO want them to have those tights in the one Queue. What
this does is allow you to grant access to a Custom Field for certain groups
"REGARDLESS of QUEUE" but also allow “additional” access to a role or some
other group on a “QUEUE-by-QUEUE” basis.
We have one group we allow full rights for any CF and they are the System
Admins for our Session. We limit this access because we do NOT want any
Tom,DIck or Harry changing values for CF’;s that someone else uses. Makes
for a messy situation.
We even have some CF’s that NO ONE can see/modify (except that 1 Admin
group) because we use those CF’s for background processing and RT updates
them automatically via scrips, no one else needs to see that info.
Hope this helps.
LBNLOn Thu, Jun 30, 2011 at 9:12 AM, Murphy, Kevin MURPHYKE@email.chop.eduwrote:
Is it possible to set up a ‘queue admin’ group that can create and
otherwise administer custom fields for tickets in a particular queue?
Under Global Group Rights, I have enabled AssignCustomFields,
AdminCustomField, and AdminCustomFieldValues.
The members of group G can create a ticket custom field, but the custom
field disappears into the ether as far as they are concerned, and they have
no way of seeing, selecting, creating values for, or assigning the newly
created custom field.
Grepping the RT source code, I also see the rights ‘ModifyCustomField’ and
’SeeCustomField’, but I don’t know where those rights are in the
2011 Training: http://bestpractical.com/services/training.html