When deactivating an account, mark New/Incomplete bugs it reported as Invalid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
When an account is deactivated, the person who reported the bug is no longer around to help with it. Because that person can no longer respond to questions or verify fixes, it might make sense to mark any untouched New or Incomplete bugs they reported as Invalid. There's a risk of throwing away a valid bug, but if someone does come across it they can reopen it and help out. If the bug's already been marked Confirmed or Triaged, then it's okay to stay as it is, but perhaps a comment could be added to the bug stating that the reporter has closed his account and will no longer receive email.
One additional thing to consider is if it makes sense to unsubscribe the person from any bugs they are currently subscribed to.
Changed in malone: | |
status: | New → Confirmed |
Changed in launchpad: | |
status: | Confirmed → Triaged |
importance: | Undecided → Low |
tags: | added: merge-deactivate |
summary: |
- When deactiving an account, mark New reported bugs as Invalid + When deactivating an account, mark New/Incomplete bugs it reported as + Invalid |
See also https:/ /bugs.edge. launchpad. net/launchpad/ +bug/238493 and https:/ /bugs.edge. launchpad. net/malone/ +bug/248223