id summary reporter owner description type status priority milestone component version severity resolution keywords cc branch changelog apichanges internalchanges 9168 milestone URL persistence john.williams@… "I've been struggling with Milestone URL persistence. It a maintenance nightmare changing milestone names. Our implementation of Trac oversees a large number of disparate university groups each with multiple milestones. Each group has their own wiki pages linking to their milestones as well as milestones of other related groups. I see ticket #364 mentioned this (jamesm about 6 years ago) >I realize its ugly, but I think that the ability to link to the milestone outweighs the benefits of a pretty-url. I would say go with a fixed integer (like tickets do) and let the user assign a name/descrption to the fixed integer. I think that the linking throughout Trac/outside Trac is more important. I agree with this statement, permanent ID's, just like tickets, elegantly solve this issue. Further, a milestone with a fixed ID having a title and description field would be highly useful. Macros (such as MilestoneDate) could pull the title into a wiki for display letting the milestone names change independently of milestone links without losing any descriptive benefits. I checked newer versions of trac hoping this was implemented, but I see no evidence * http://trac.edgewall.org/demo-0.12/milestone/Feed%20the%20dogs Link to a milestone I created but then changed the name * http://trac.edgewall.org/demo-0.12/milestone/My%20name%20WILL%20change * http://trac.edgewall.org/demo-0.12/milestone/My%20name%20changed " enhancement new normal next-major-releases roadmap 0.10.5 major milestone, traclinks