All, I re-worked the trac.ini configuration quite a bit, and got things working to a level that I think they're ready for discussion. There is a lot of cleanup left, some permission checking stuff that isn't done, little error checking, etc.
The workflow-experiment sandbox has 4 example workflows: trivial, simple, opensource, and enterprise. Each is in a <name>-workflow.ini file in the top directory, and can be inserted into a trac.ini. The workflows have these states: trivial: new, closed simple: new, accepted, closed opensource: new, assigned, accepted, started, closed enterprise: new, assigned, in_work, in_QA, closed Each transition can have a list of operations: owner_del - clears the owner owner_set - sets the owner to the selected user owner_set_to_self -sets the owner to the logged-in user resolution_del - clear the resolution resolution_set - set the resolution The opensource workflow is based on the description that Christian gave on March 6th, but with some differences. - assigning to yourself != accepting. You have an accept action, use it. - if you accept a ticket you do not own, you also get ownership - reassigning a started ticket puts it in assigned state; it needs to be accepted or started by the new owner The enterprise workflow adds a QA step for validating things are correct. And it drops the "accepted" state. The simple workflow is close to what we currently have in Trac. The trivial workflow is to show the degenerate case. First of all, this won't address all conceivable workflows, but I believe it should be flexible enough to address most of them. Adding more complex nuances to the workflow would require replacing this TicketActionController. Second, I don't like the way it looks in the .ini; it's very verbose. Reasonable defaults would probably help a lot here, but it still feels awkward. I do like having all of it in one section instead of two, though. Third, I branched off the workflow branch because this is primarily for discussion purposes. If people like it, I can clean up the workflow branch from the beginning. So, I'm interested in what people think about: - this approach to a basic configurable workflow - the 4 example workflows and their usefulness/applicability Discuss. I'll join in the discussion on Monday. Eli --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
