Hello, Whatever implementation is chosen, I would consider this as an important part of the new custom workflow functionality.
The http://trac.edgewall.org/wiki/NewWorkflow#Changesfornewworkflow lists additional changes in Trac 0.8 that has been made in order to complete the workflow support in Trac: - Reports need to be updated to handle common cases of workflow customization - Milestones need to support new statuses - Timeline Regards, Pavel On 9/11/07, Christian Boos <[EMAIL PROTECTED]> wrote: > > > Hello, > > I'd like to reach a decision for ticket #5572 (Roadmap Progress bar > errors when using custom Workflow). Again a bug report that turned into > a new feature ;-) > More seriously, the motivation here was to match the flexibility offered > by the ConfigurableTicketWorkflow. As you know, with the stock > ITicketActionController you can define simple customized workflow, and > define new ticket states in the config files. I think it would be > suboptimal to /not/ have the possibility to be able to tell how those > new states should be grouped in the milestone display. > > Hence the following patch: > > http://trac.edgewall.org/attachment/ticket/5572/milestone_groups-r5946.diff > > which was refined a few times by me and ecarter. > Noah expressed his concerns that this would be too much for Trac core. > > A simpler fix would be possible (one group for closed tickets, a second > for all the other states), but as I said above I think it's just at the > appropriate level of complexity, matching the workflow configurability. > > Opinions? > > -- Christian > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
