To list,
I'm not using 3.8 yet, but I was hoping that perhaps the permissions
had been modified a bit to allow a user from one queue to “link” his
ticket to a ticket in another queue without having to have the
"ModifyTicket" privilege. I have many queues that could have their
tickets linked to tickets in other queues, but don’t want the support
personnel of those other queues to be able to modify tickets in their
own. Does that make any sense?
Kenn
LBNL
This rightvfor strict link acl checking was added in 3.6 or soOn Aug 29, 2008, at 1:55 PM, Kenneth Crocker KFCrocker@lbl.gov wrote:
To list,
I’m not using 3.8 yet, but I was hoping that perhaps the
permissions
had been modified a bit to allow a user from one queue to “link” his
ticket to a ticket in another queue without having to have the
“ModifyTicket” privilege. I have many queues that could have their
tickets linked to tickets in other queues, but don’t want the support
personnel of those other queues to be able to modify tickets in their
own. Does that make any sense?Kenn
LBNL
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
I’m not using 3.8 yet, but I was hoping that perhaps the permissions
had been modified a bit to allow a user from one queue to “link” his
ticket to a ticket in another queue without having to have the
“ModifyTicket” privilege. I have many queues that could have their
tickets linked to tickets in other queues, but don’t want the support
personnel of those other queues to be able to modify tickets in their
own. Does that make any sense?
I can’t tell if you don’t want to hand out ModifyTicket to these
users at all or if you’re ok letting them have ModifyTicket in their
own queue.
If the latter, StrictLinkACL in your config may help.
If the former, there is some rather tangled code that would
need untangling to do what you want.
-kevin
Kevin,
My situation is that these queues are completely seperate support
groups and very seldom do they work on the same issue. This is for those
tickets where one support group needs another group to complete their
work in order for the first group to complete theirs. The “DependsOn”
link is perfect, but to do that, I have to allow the “ModifyTicket”
right for group1 to a queue they normally do not touch. Not very secure.
But thanks.
Kenn
LBNLOn 8/29/2008 4:46 PM, Kevin Falcone wrote:
On Aug 29, 2008, at 4:55 PM, Kenneth Crocker wrote:
I’m not using 3.8 yet, but I was hoping that perhaps the permissions
had been modified a bit to allow a user from one queue to “link” his
ticket to a ticket in another queue without having to have the
“ModifyTicket” privilege. I have many queues that could have their
tickets linked to tickets in other queues, but don’t want the support
personnel of those other queues to be able to modify tickets in their
own. Does that make any sense?I can’t tell if you don’t want to hand out ModifyTicket to these
users at all or if you’re ok letting them have ModifyTicket in their
own queue.If the latter, StrictLinkACL in your config may help.
If the former, there is some rather tangled code that would
need untangling to do what you want.-kevin
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com