| 2008-01-02 09:37:06 |
Matthew Paul Thomas |
bug |
|
|
added bug |
| 2008-01-04 22:10:13 |
Diogo Matsubara |
malone: status |
New |
Confirmed |
|
| 2008-01-04 22:10:24 |
Diogo Matsubara |
malone: importance |
Undecided |
Medium |
|
| 2008-02-13 00:11:46 |
Eleanor Berger |
malone: assignee |
|
intellectronica |
|
| 2008-02-13 00:11:46 |
Eleanor Berger |
malone: milestone |
|
1.2.2 |
|
| 2008-02-13 02:52:02 |
Matthew Paul Thomas |
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". |
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, *whenever* a project switches from not using Launchpad for bug tracking, to using it, all its "Unknown" bugs should be changed to "Undecided". |
|
| 2008-02-13 07:55:08 |
Björn Tillenius |
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, *whenever* a project switches from not using Launchpad for bug tracking, to using it, all its "Unknown" bugs should be changed to "Undecided". |
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, *whenever* a project switches from not using Launchpad for bug tracking, to using it, all its "Unknown" bugs should be changed to "Undecided". This particular change is not part of this bug report, though. It should be dealt with separately. |
|
| 2008-02-15 01:07:05 |
Matthew Paul Thomas |
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, *whenever* a project switches from not using Launchpad for bug tracking, to using it, all its "Unknown" bugs should be changed to "Undecided". This particular change is not part of this bug report, though. It should be dealt with separately. |
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. |
|
| 2008-02-15 10:36:56 |
Eleanor Berger |
malone: status |
Confirmed |
In Progress |
|
| 2008-02-18 11:41:14 |
Eleanor Berger |
malone: status |
In Progress |
Fix Committed |
|
| 2008-02-25 20:20:06 |
Eleanor Berger |
malone: status |
Fix Committed |
Fix Released |
|
