Warning when associated branch doesn't have a bug task
Bug #760889 reported by
Ted Gould
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Currently there is a list of associated branches with a particular bug. There is no limitation on which projects those branches are filled on (and I think that's a good thing), but this means that they could either be on the wrong project or the bug could be misfilled. I think that there should be some visual signal next to the related branches if they're on projects that don't have bug task in the bug. It would also be nice if the same signal was put on the bugs associated with the branch page.
Thanks.
| tags: | added: branches bugs |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: ui |
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 760889] Re: Warning when associated branch doesn't have a bug task | #2 |
To post a comment you must log in.
I think the technical summary is to show a warning when the branch target, adapted to a bug target, is not present in the bugs bugtasks' targets.
I do not think there is a one to one relationship between branch target and bug target. branch targets are mostly a subset of bug target, except for source package. The code could not warn about a branch for a source package linked to a bug, though that bug and one of the branches may be for distribution source package