On Thu, Jun 26, 2008 at 11:54:02AM +0300, Jani Tiainen wrote: > Is ticket, once issued, on the system locked to type it has? Currently > Trac is very liberate in this sense and allows change of issue type > which fits well to "staying away" philosophy. > > Restrictions like different workflows pushes Trac usage to more "getting > in a way" philosophy.
This reminds me a lot of Change + Synergy - the worst example of "always in your way" I had to encounter so far. > I see following solutions to this: ... > * Require default state for each ticket type and set that in > case of change Sounds harsh, but might be the simplest (nearly always = best) solution both from the implementation and the user POV. > * Add change-on-copy functionality (similiar to Redmine) What would be the consequences of copying? Would one loose e.g. history information? Cheers. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
