"Related branches" for a bug with multiple git merge proposals gets confused about reviewers
Bug #1793283 reported by
James Henstridge
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Colin Watson | ||
Bug Description
On the following bug, there are three related merge proposals:
https:/
All three merge proposals are between the same pair of git repositories, but different branches.
The summary shows the same four reviewers for each merge proposal, when in reality it is four reviewers total spread over the three merge proposals (two reviewers on one, one reviewer on each of the other two).
Related branches
lp:~cjwatson/launchpad/fix-mp-vote-preloading
- William Grant: Approve (code)
-
Diff: 81 lines (+29/-3)2 files modifiedlib/lp/code/model/branchmergeproposal.py (+5/-1)
lib/lp/code/model/tests/test_branchmergeproposal.py (+24/-2)
Revision history for this message
| James Henstridge (jamesh) wrote | #1 |
Revision history for this message
| Colin Watson (cjwatson) wrote | #2 |
| tags: | added: code-review lp-code regression |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Colin Watson (cjwatson) |
| status: | Triaged → In Progress |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #3 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
My mistake: one of the merge proposals has a different source repository. All three have the same destination git repository though.