On Wednesday 25 April 2007, Christian Boos wrote: > > Eli Carter wrote: > > ... > > At that point, I'll merge this back into the main workflow branch. > > > > Comments and feedback more than welcome, > > I looked at the changes and tested the branch. It all looks good to me. > I have some minor nits about the Status filter, which reads like this > when using the opensource workflow: accepted, assigned, closed, > infoneeded, infoneeded_new, new, started. > - the alphabetical ordering doesn't look that interesting; it'd be > better to at least start with 'new' and end with 'closed'
I'm not sure that [new, alphabetical..., closed] would be an improvement though. Alphabetical gave me a definitive order, which I believe is a slight improvement over semi-random. As it stands, the .ini is action-centric, so there isn't a straightforward way to determine ordering of states. A graph-based ordering of some sort may be the RightWay(tm) to do this. > - then the presence of two infoneeded status will be for sure > surprising for the end user; I know why there are two such states, but > we should find some way to make the interface friendlier. Ah, yeah, I hadn't really thought about that. Agreed, but we need to be careful not to confuse the user by obscuring what the state is. (In other words, I don't think we should make "needinfo" mean "needinfo or needinfo_new".) > I'm +1 for integrating these changes in the main workflow branch. Thanks. > Speaking of the main branch, I'm quite OK with it, I still have to test > the additional plugins, but the way it already works with, e.g. the > opensource workflow is quite satisfying. > One minor improvement would be to be able to specify the order of the > actions. > E.g. on a new ticket, you have: leave, resolve, requestinfo, assign and > accept. > Having: leave, requestinfo, assign, accept and resolve would be > preferable here, and I think it should be possible to achieve this by > adding an .order attribute to the actions. That's what the .default attribute does. The larger that value, the higher on the list the action will be. It defaults to 0, and can be negative. The first action is the action that is selected by default. The current workflows set the leave action to a weight of 1, provideinfo as 2, and leave the rest as 0. Suggestions on what those should be are welcome. (Guess I'd better figure out where the right place to document all these bits about the .ini syntax is.) Thanks, 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 -~----------~----~----~----~------~----~------~--~---
