RT 3.4.5/AT 1.2.3
I noticed that if a user has global ModifyCustomField rights, they can
change custom field values in any ticket/asset, even if they don’t have
ModifyTicket/ModifyAsset for the ticket/asset. This seems very odd as
the CFs are clearly part of the ticket/asset.
I need users to be able to click a lot of custom field values when
opening tickets in certain queues and the only way I can find to allow
this is using the Global ModifyCustomField right as this right doesn’t
exist for Queues or Assets. I really don’t want it global as users
should be able to modify custom fields when opening a ticket in a queue
that uses custom fields but I certainly don’t want them to be able to
modify any custom fields in any asset, which this right lets them do.
Any ideas appreciated. I tried assigning ModifyCustomField to the
Requestor Role only so they don’t get the right on assets but this seems
to not work - I can’t modify any ticket custom fields any more and it
only works again when I put the right back on the global Privileged
group.
PK
Philip Kime
NOPS Systems Architect
310 401 0407
RT 3.4.5/AT 1.2.3
Any ideas appreciated. I tried assigning ModifyCustomField to the
Requestor Role only so they don’t get the right on assets but this
seems to not work - I can’t modify any ticket custom fields any more
and it only works again when I put the right back on the global
Privileged group.
Create a group for each set of users (if you haven’t already) and assign
the ModifyCustomField right for each individual custom field to the
group. Use RTx::RightsMatrix to make it easier.
HTH
Joshua Colson jcolson@voidgate.org
Perfect, this works, thanks. It still seems to be a bit strange that
Custom fields aren’t considered part of a ticket/asset for the
ModifyTicket/ModifyAsset rights …
PK-----Original Message-----
From: Joshua Colson [mailto:jcolson@voidgate.org]
Sent: 30 May 2006 13:17
To: Philip Kime
Cc: RT users
Subject: Re: [rt-users] Confused by Custom field rights
Create a group for each set of users (if you haven’t already) and assign
the ModifyCustomField right for each individual custom field to the
group. Use RTx::RightsMatrix to make it easier.
HTH
Joshua Colson jcolson@voidgate.org
Philip Kime wrote:
Perfect, this works, thanks. It still seems to be a bit strange that
Custom fields aren’t considered part of a ticket/asset for the
ModifyTicket/ModifyAsset rights …
PK
-----Original Message-----
From: Joshua Colson [mailto:jcolson@voidgate.org]
Sent: 30 May 2006 13:17
To: Philip Kime
Cc: RT users
Subject: Re: [rt-users] Confused by Custom field rights
Create a group for each set of users (if you haven’t already) and assign
the ModifyCustomField right for each individual custom field to the
group. Use RTx::RightsMatrix to make it easier.
HTH
–
Joshua Colson jcolson@voidgate.org
The rt-users Archives
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
We’re hiring! Come hack Perl for Best Practical: Careers — Best Practical Solutions
Philip,
Actually, since it only makes sense to give privileges to groups and
then add users to groups (that way you are not continually doing the
same redundant work for every user you want to get to a Queue and you
don’t have tons of users’ rights to maintain) it also makes sense to do
the same thing for custom fields. If a GROUP has certain rights to a
Queue (set up in configuration) and a Custom field can be applied to any
number of Queues, it allows more flexibility to also require group
access to a custom field, because you may have more than 1 group
accessing a Queue and one group you may WANT to modify custom fields and
another you don’t. Does that make sense?
Kenn
Actually, you’re quite right - I hadn’t factored in that CFs can be
applied to different Queues.
PKFrom: Kenneth Crocker [mailto:KFCrocker@lbl.gov]
Sent: 01 June 2006 09:53
To: Philip Kime
Cc: Joshua Colson; RT users
Subject: Re: [rt-users] RE: Confused by Custom field rights
Philip Kime wrote:
Perfect, this works, thanks. It still seems to be a bit strange that
Custom fields aren’t considered part of a ticket/asset for the
ModifyTicket/ModifyAsset rights …
PK
-----Original Message-----
From: Joshua Colson [mailto:jcolson@voidgate.org]
Sent: 30 May 2006 13:17
To: Philip Kime
Cc: RT users
Subject: Re: [rt-users] Confused by Custom field rights
Create a group for each set of users (if you haven’t already) and
assign the ModifyCustomField right for each individual custom field to
the group. Use RTx::RightsMatrix to make it easier.
HTH
–
Joshua Colson jcolson@voidgate.org
The rt-users Archives
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
We’re hiring! Come hack Perl for Best Practical:
Careers — Best Practical Solutions
Philip,
Actually, since it only makes sense to give privileges to groups and
then add users to groups (that way you are not continually doing the
same redundant work for every user you want to get to a Queue and you
don’t have tons of users’ rights to maintain) it also makes sense to do
the same thing for custom fields. If a GROUP has certain rights to a
Queue (set up in configuration) and a Custom field can be applied to any
number of Queues, it allows more flexibility to also require group
access to a custom field, because you may have more than 1 group
accessing a Queue and one group you may WANT to modify custom fields and
another you don’t. Does that make sense?
Kenn