Hi That actually sounds cool, but unfortunately I don't have time for it.
I will try to create a new action (like set_owner and the unofficial set_owner_to_reporter) in default_workflow.py and name it set_owner_to_prev_owner. Is it ok to make an sql call from default_workflow.py or is there some other preferred way to do it? Cheers / Erik On 8/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Sounds like a good idea! > > It would be even cooler if you were able to set the ownership to the > last owner in a particular group of users (QA <-> Developers). > That way it it would be easy to pass the ownership between the last > responsible developer and the last responsible Q/A. > > > > Cheers > Jim > > > On 13 Aug, 10:34, "Erik Andersson" <[EMAIL PROTECTED]> wrote: > > Hi > > > > I'm working on a workflow where I for example in_QA want to provide the > > possibility to automatically assign a ticket to the back to the previous > > owner. Has anyone else already done this? > > > > I'm thinking that the two options is to write a nested sql that gets the > > second latest entry from the ticket_change table or that I get all owner > > entries from the table and then get the second latest entry in the > python > > code. > > > > Anyone else that got any better ideas? > > > > Cheers / Erik > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
