I think you're missing the point though. If you don't allow
Stealticket then this wouldn't matter. The only question is if they
can Steal the ticket, why force them to take duplicate steps ?
I don't understand why you don't want more control for Bulk Update.
So any of your users can
On Thu 5.Mar'09 at 2:11:34 -0800, Jo Rhett wrote:
I think you're missing the point though. If you don't allow Stealticket
then this wouldn't matter. The only question is if they can Steal the
ticket, why force them to take duplicate steps ?
Because Steal isn't the same thing as Take.
Jo Rhett,
I only grant ticket owners the ModifyTicket right, so noone CAN
bulkudate a ticket that isn't theirs.
Kenn
LBNL
On 3/5/2009 2:11 AM, Jo Rhett wrote:
I think you're missing the point though. If you don't allow Stealticket
then this wouldn't matter. The only question is
On Mar 5, 2009, at 10:16 AM, Jesse Vincent wrote:
On Thu 5.Mar'09 at 2:11:34 -0800, Jo Rhett wrote:
I think you're missing the point though. If you don't allow
Stealticket
then this wouldn't matter. The only question is if they can Steal
the
ticket, why force them to take duplicate
On Mar 5, 2009, at 2:32 PM, Kenneth Crocker wrote:
I only grant ticket owners the ModifyTicket right, so noone CAN
bulkudate a ticket that isn't theirs.
For your environment that may make sense, but not here. OTRS enforces
that kind of approach -- you can't turn it off without
I just observed something odd. While closing a ticket (but not at any
other time I have found) if you change the Owner of the ticket you
will see this in the results:
You can only take tickets which are unowned.
...and the owner is not changed. Now this is odd because every
Privileged
Reading the code in Ticket_Overlay around line 2730-2750 it would
appear that this is deliberate. For someone to reassign a ticket to
someone else on their reply, they must be the current owner. For me
to take it back and close it, I need to separately Steal it, then
Resolve it.
Would
On Wed 4.Mar'09 at 11:29:38 -0800, Jo Rhett wrote:
Reading the code in Ticket_Overlay around line 2730-2750 it would
appear that this is deliberate. For someone to reassign a ticket to
someone else on their reply, they must be the current owner. For me
to take it back and close it,
On Mar 4, 2009, at 11:33 AM, Jesse Vincent wrote:
On Wed 4.Mar'09 at 11:29:38 -0800, Jo Rhett wrote:
Reading the code in Ticket_Overlay around line 2730-2750 it would
appear that this is deliberate. For someone to reassign a ticket to
someone else on their reply, they must be the current
Jo Rhett,
I agree with Jesse. Although it is a pain in the rump to have to go
thru 2 steps to re-assign a ticket, I am of the mind that when you
lossen the the reins of ownership (and for that matter let too many
users have the ModifyTicket right.) you run the risk of owners
undoing
10 matches
Mail list logo
