On Saturday 17 May 2008 05:48:51 pm Jeff Snider wrote: > For our local installation, I've done a little bit of work to add > function like operations with parameters to the default_workflow > engine. For instance, we have a set_owner(foo) operation now. As I > recall it was simple to add. Perhaps something similar could be used?
Um. You shouldn't need to add that; myaction.operations = set_owner myaction.set_owner = foo is supported. So is: myaction.operations = set_owner myaction.set_owner = foo,bar,baz > Essentially make the timeline code dumb about ticket states, and leave > it up to the workflow to tell the timeline what to do. A new > operation like note_in_timeline(sent to qa) might work. For i18n > support, keep the default workflow words in the localization files and > refer to them using an identifier, such as > note_in_timeline(i18n:created). Not perfect, but it may be good > enough for now. > > To make that work for new tickets though, you'd probably need the > ticket creation to invoke a specific workflow action automatically, so > it would have a chance to run that operation. That might be handy > anyway to run other operations as well, or even set a different > starting status. > > Eli, to answer your initial question, I think the way it is now is odd > but usable. Since it's not impeding the use of tickets or custom > workflow, and seeing as 0.11 is already in rc, I think 0.11.1 would be > ok. Thanks for the feedback on this. Eli ------------------. "If it ain't broke now, Eli Carter \ it will be soon." -- crypto-gram [EMAIL PROTECTED] `------------------------------------------------- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
