thanks for suggestions! think cloning won't be an option (evil duplication) because tickets and their resolutions often refer to the same software-artifacts and inconsistency is a bad virtue.
the reason why we cannot decide one ticket to one milestone is that in some circumstances we have parallel milestones (as seen from dates). and sometimes a feature is relevant to these parallel milestones (discussion something like: "yes feature would be nice for this exhibition and for that one"). this Set semantics of ticket to milestones is of course an exception, but occurs from time to time and should be expressed by the tool. i will have a look to the Masterticket plugin. On Dec 6, 10:05 am, "Erik Andersson" <[EMAIL PROTECTED]> wrote: > Hi > > Somehow you must anyway decide on what should be implemented for each > release/milestone? > > You could use the masterticket plugin and use a masterticket(connected to a > feature milestone?) for all functionality and two other tickets, blocking > the masterticket, for each release/milestone? > > Cheers / Erik > > On Dec 6, 2007 9:51 AM, Christian Boos <[EMAIL PROTECTED]> wrote: > > > > > aldana wrote: > > > hi, > > > > in our software-development it is possible that a ticket is relevant > > > to two milestones, that means milestones distinguish themselves within > > > deadlines but features are included in scope of two milestones. > > > > how can i change that inside ticket edit i can choose multiple > > > milestones (semantics of a set)? > > > Short answer: you can't. > > > Longer answer: this has already been discussed at length, there are > > several possibilities for future versions of Trac. But right now, only a > > few workaround exists, neither is completely satisfying: > > - simply mention the other milestones in the ticket wiki texts (the > > description or a comment) > > - use a custom field (but beware, we still don't have the "wikitext" > > kind of field yet) > > - clone the ticket and use one for each milestone > > > For reference: > > - tickets linked to multiple versions: > >http://trac.edgewall.org/ticket/4298 > > - Ticket duplication using Trac:http://trac.edgewall.org/ticket/4686 > > > -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
