Thanks Christian! http://trac.edgewall.org/ticket/5658
Actually, i ran into this for the same reasons that "mape" writes in a comment to ticket:5658 a situation where you want to visualize the milestone over time can actually only work when running through active tickets. This is necessary because milestones don't have an explicit start date -- you have to calculate it to show a burndown chart with a start date. (and tickets that are active before they are retargeted should not change the startdate of the new milestone) With Trac's current domain model, what would be the smallest possible change to make sure a milestone start date can be calculated. /Jesper On Apr 1, 12:01 pm, Christian Boos <[email protected]> wrote: > Jesper Rønn-Jensen wrote: > > Hey there. > > > It kind of surprised me to see this behaviour in Trac 0.11.3: > > > I close a milestone and select to "Retarget associated open tickets to > > milestone:" > > > After this, none of my open tickets reflect the milestone change in > > ticket_change. How come? > > > Are there other inconsistencies in the use of ticket_change that I > > should be aware of? > > > Is this a bug or a feature? > > http://trac.edgewall.org/ticket/5658 > > Nearly in the same terms as your summary ;-) > > -- 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 -~----------~----~----~----~------~----~------~--~---
