possible to change bug status / importance after it is converted to a question
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Looking at bug 222569 - the bug squad has noticed that the bug is converted to a question but it has a status of Incomplete. It appears that someone had not refreshed the bug report after it had been converted to a question and then changed the status to incomplete. I've recreated the same issue on staging by opening a bug in 2 tabs and converting it to a question in one tab and then setting the status in the other tab.
It seems that the ability to modify the bug report, after it is converted to a question, is only locked down in the web user interface and that one would be able to modify a bug's importance and status after it has been converted into a question using the api.
This is problematic because the example bug now shows up in Incomplete bug lists but nothing can be done with it using the web interface.
| Eleanor Berger (intellectronica) wrote | #1 |
| Changed in malone: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in launchpad: | |
| importance: | Medium → Low |
I can reproduce, and the cause is indeed as suggested. Setting importance to Medium because even though it's quite difficult to trigger this from the UI, this will be exposed more when bug tasks are accessed using the API.