Bugs +editstatus page forces removal of closed milestone

Bug #1157937 reported by dobey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

If there are many bug tasks on a bug, Launchpad forces you to go to the +editstatus page, breaking the ajax editing of bug task fields. However, when using the +editstatus page, to change the status of a task from "Fix Committed" to "Fix Released" for a milestone that has been released, the bug task's targeting to that milestone is force-removed, by Launchpad complaining about an error when the value is left in the drop-down. Only by setting the bug to an active milestone, or no milestone, can one continue. This causes the bug to no longer show up on the milestone's page, and disassociates the bug from that milestone completely.

Changed in launchpad:
status: New → Triaged
importance: Undecided → High
tags: added: bugs milestones regression
Curtis Hovey (sinzui)
tags: removed: regression
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.