It is not obvious to users how to cause a proposal that was created without a prerequisite branch to become a proposal with a prerequisite branch
Bug #596796 reported by
Steve Kowalik
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
Original request: I have an MP I'd like to change to depend on an pre-req branch, and I can't edit the MP to do so. This should be possible, and then should tag the diff so it gets regenerated.
Based on code team feedback:
When a user wants to change an MP to have a different prerequisite branch than it was originally filed with, they should be able to see how to do that very easily (and it will probably be implemented by causing a resubmit).
Changed in launchpad-code: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in launchpad: | |
importance: | Medium → Low |
To post a comment you must log in.
We don't want to allow adding a prerequisite branch to an existing merge proposal, because adding (or removing, or changing) a prerequisite branch changes the meaning of the merge proposal, and therefore invalidates any reviews or approval that may have been done.
Instead, we want to support using resubmit to change the involved branches. See bug #504369.