id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,branch,changelog,apichanges,internalchanges 3718,Trac should use HTTP 301 Moved when milestones get renamed,daniel.connor@…,," 1. Create a milestone ""Example"" 2. Add a ticket to the milestone 3. Subscribe to the RSS feed. 4. Edit the milestone, rename to ""Changed Milestone"" Expected behaviour: Trac 'knows' a milestone has been renamed, and does a 301 Moved response code. The client application / browser redirects, and the end user doesn't notice anything out of the ordinary Actual: Trac doesn't do this. milestone:""milestone name"" links break, feeds break, and so much more. Suggested: A simple entry to a 'milestone (previous) names' table would fix this - when a milestone isn't known, the table is checked, and a 301 is sent with an updated location. ",enhancement,new,high,next-major-releases,general,0.9.6,major,,redirect rename tracobject consider,,,,,