"Unknown" importance should be unsettable if project uses Launchpad for bugtracking

Bug #179816 reported by Matthew Paul Thomas
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Eleanor Berger

Bug Description

1. Open a bug report in a project for which you have permission to set bugs' importance.
2. Set its importance to "Unknown", and choose "Save Changes".

What happens: The bug's importance is set to "Unknown".
What should happen: "Unknown" shouldn't even be an option, because it exists only for bug watches, and the bug you're dealing with is in a project that uses Launchpad for bugtracking.

Suggested data migration: All bug reports that currently have "Unknown" importance, in projects that use Launchpad for bugtracking, should be changed to "Undecided".

Similarly, a bug's importance should be changed from "Unknown" to "Undecided" *whenever* the project it is filed against switches from not using Launchpad for bug tracking, or whenever it is retargeted from a project that doesn't use Launchpad for bugtracking to one that does. This particular change is not part of this bug report, though. It should be dealt with separately.

Tags: lp-bugs
Changed in malone:
status: New → Confirmed
importance: Undecided → Medium
Changed in malone:
assignee: nobody → intellectronica
milestone: none → 1.2.2
description: updated
description: updated
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

If, as part of the fix for this bug, "Unknown" bugs are not changed to "Undecided" whenever a project switches to using Launchpad for bug tracking, then Launchpad could still contain bug reports with "Unknown" importance filed against projects that use Launchpad for bug tracking. Therefore, when that automatic conversion *was* implemented, the data migration would need to be done again to ensure we'd caught all the errant bug reports.

The data migration could be done just once, at that later stage, but that would leave bug reports with the wrong Importance value between now and then. It might also cause awkwardness with the Importance menu having to include "Unknown" as an option only if that was the existing importance level, and not otherwise.

Revision history for this message
Eleanor Berger (intellectronica) wrote :

It's a bit of a shame to leave existing projects with this status for a bit longer, but it won't create any (additional) problem. The correct status will be displayed, and we'll do the migration later.

description: updated
Revision history for this message
Eleanor Berger (intellectronica) wrote :

See bug #192011 for the proposed migration

Revision history for this message
Eleanor Berger (intellectronica) wrote :

See bug #192015 for the requirement to convert the importance when a project switches to using Launchpad for bug tracking

Changed in malone:
status: Confirmed → In Progress
Revision history for this message
Eleanor Berger (intellectronica) wrote :

RF 5704

Changed in malone:
status: In Progress → Fix Committed
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Reported bug 193505 for the retargeting case.

Changed in malone:
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote :

"Unknown" still shows up as an advanced filter search option at https://bugs.launchpad.net/ubuntu/+bugs?advanced=1 . Should that be a separate bug report?

Revision history for this message
Eleanor Berger (intellectronica) wrote :

> "Unknown" still shows up as an advanced filter search option ...

Yes. See bug #195570

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.