A user with limited permissions can change a bug status, but cannot revert back to "triaged"
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Assume there is a bug on a status such as "triaged" which requires certain permissions to change the status to this.
A new user comes along, likes the look of that bug, and attempts to fix it. They assign themselves, and set the status to "In progress" to show others they are working on it.
They may find it too much to do that particular bug (skill level, time commitment, etc etc), and decide to give it back to the wider community to fix. They can then unassign themselves, but they can't put the status back to the original status of "triaged".
I would suggest that if a user is able to change a status *from* something, they should be given permissions to change that particular bug's status *back* to that status. This also gives a way to undo a accidental click.
Cheers,
Hugh
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: bugs |
| summary: |
- A user with limited permissions can change a bug status to something - like "In progress", then can't change it back to what it was (like - "triaged" or "confirmed" + A user with limited permissions can change a bug status, but cannot + revert back to "triaged" |
