misleading bug status in bugs affecting multiple projects
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Invalid
|
Undecided
|
Unassigned |
Bug Description
If one bug[1] has more than one project affecting it, only the newest project entry is shown in the "Report a bug" form, when a summary has been entered and the system presents a list of possible bug candidates to eliminate duplicates. However, the newest project might not be the one that this bug affects primarily. In this example[1], the bug affected 3 projects initially, but was narrowed down to one project. In consequence, the other two were set to "invalid", which ultimately shows as the bug status in the "report a bug" view.
I therefore suggest to change the behavior of the list overview in the "report a bug" form to first filter by status (ordering the "invalid" status last) and then choosing the project and status to display by some other means (like the current way of taking the last affected project added).
_______
[1] e.g. https:/
affects: | launchpad → malone |
The function for choosing which context to show should be the same function used to fix bug 2816.