It would be nice to be able to link merge proposals to each other when one MP depends on work in a second MP

Bug #1916785 reported by Jeff Lane 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

We often work on a single umbrella project that has several sub-projects underneath. Specifically this is work on Checkbox and the many, many checkbox providers that are used for cert, regression testing and so forth.

Very often, we will have a task that spans LP projects... for example:

Adding a new script and job definition to plainbox-provider-checkbox
Modifying testplans to use the new script and job definition in plainbox-provider-certification-*

Currently, there is no easy way to link those different MPs to each other to help ensure that they are reviewed together. We can somewhat work around this using comments on the MPs but that's clunky.

One can already tie an MP to one or more bugs (and on bugs tie one or more MP to the bug). It would be really helpful if that were extended a bit so we could tie MPs to each other as well.

Something like on the Merge Proposal summary page, below the Related Bugs: line there's a "Related Merge Proposals" line:

Related bugs: 1234567
Related merge proposals:
  <Link to related MP for Project A>

That way one will quickly and easily see that MP-A is related to/dependent on MP-B and that the two should be reviewed together.

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.