Bug reporter should be retroactively marked as affected for unresolved bugs
Bug #318193 reported by
Thinboy00
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
To reproduce:
1. Have an unresolved bug report you opened from before the "this bug affects me too" feature was implemented
What happens:
You have to manually mark yourself as affected using the aforementioned feature
What should happen:
The system automagically and retroactively marks the reporter as affected (unless the bug has been resolved), since this is almost always the case.
A similar problem exists for newly opened bugs.
| description: | updated |
Revision history for this message
| Brian Murray (brian-murray) wrote | #1 |
| affects: | launchpad-report-tool → malone |
Revision history for this message
| Björn Tillenius (bjornt) wrote | #2 |
| Changed in malone: | |
| importance: | Undecided → Medium |
| milestone: | none → 2.2.4 |
| status: | New → Triaged |
Revision history for this message
| Björn Tillenius (bjornt) wrote | #3 |
| Changed in malone: | |
| importance: | Medium → Undecided |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
This bug was incorrectly filed about the Launchpad Bug Report Tool which has nothing to do with the backend for Launchpad or the bugs portion of Launchpad. Subsequently, I'm changing the project affected to Malone which is the bugs portion of Launchpad.