[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rt-devel
Subject:    Re: [Rt-devel] re-assigning tickets
From:       Jesse Vincent <jesse () bestpractical ! com>
Date:       2008-12-21 22:08:32
Message-ID: 20081221220832.GC1271 () 17h ! local
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Sun 21.Dec'08 at 22:28:03 +0100, Richard Hartmann wrote:
> 2008/12/21 Jesse Vincent <jesse@bestpractical.com>:
> 
> > And that's how it needs to be to make ownership make any sense at all as
> > a ticket locking mechanism...
> 
> Locking on the user level can make sense, but for people who need to
> re-assign tasks on a regular basis, it's an extra step which creates more
> work.
> I.e. if people have the right to do this something in a particular organization
> shouldn't the tool, RT in this case, adapt to that?

It's easy to build an extension to do "force owner change". I'd strongly
recommend that if you build such a thing you _not_ make it happen any
time the user changes the owner, but only when they click a particular
button.  (You can use bulk update's "force owner change" option as a
template).

> 
> 
> Richard
> _______________________________________________
> List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
> 

-- 

[Attachment #5 (application/pgp-signature)]

_______________________________________________
List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel


[prev in list] [next in list] [prev in thread] [next in thread]