[rt-users] Prevent updates to tickets that have been updated since you've opened it

[Joel Schuweiler]

Ken,

No, I want multiple people to update a ticket. I don't want someone to 
submit a change to a ticket if they haven't seen a more recent change.

A prime example would be svn, when you try to check in something out of 
date you're not allowed to until you do an update, which forces you to 
deal with any conflicts that may arise.

-Joel

Kenneth Crocker wrote:
> Joel,
>
>
>     What is the purpose? Are you trying to keep multiple people from 
> updating the same ticket? If, so, there is a much easier way to do it.
>
> Kenn
> LBNL
>
> On 3/3/2008 3:18 PM, Joel Schuweiler wrote:
>> In large queues I find that a source of  'confusing/messy/ugly/wrong' 
>> tickets come from someone doing the following:
>>
>> 1) person 1 opens a ticket
>> 2) person 2 opens the ticket and updates
>> 3) person 1 updates the ticket
>>
>> person 1 and person 2 can both be internal, or one can be external, 
>> either case it makes for a very confusing situation. I'm thinking 
>> about looking into the following
>>
>> 1) person 1 opens a ticket
>> 2) person 22 opens the ticket and updates
>> 3) person 1 updates the ticket
>> 4) rt sees that the last modified time has changed since last update
>> 5) pops them to an error page saying the ticket has been updated 
>> since they last looked, and pre-fills all the fields for them
>>
>> Can anyone see any issues with this?
>>
>> (more technical)
>> 1) submit the last modified time as a hidden input
>> 2) add it to the sql such that the statement fails (no wasted time 
>> making an extra statement to compare before insert)
>>
>> -Joel
>> _______________________________________________
>> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>>
>> Community help: http://wiki.bestpractical.com
>> Commercial support: sales at bestpractical.com
>>
>>
>> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
>> Buy a copy at http://rtbook.bestpractical.com
>>
>