Person's related bug pages hides duplicates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
I commented on Ubuntu bug #576171. Later this bug was marked as duplicate of #571743. This made the bug stop showing on my Launchpad homepage in the Bugs participation list. I had not written down the bug number, so I could not find the bug I commented on anymore. It looked like the bug had disappeard from Launchpad.
I wish I would not lose the link to the bugs that I comment on. It was a lot of bother to find the bug again, and discover the proposed solution (which was correct, update went OK). Marking as duplicate was OK in this case, it just had the unfortunate side effect of making me not find the bug anymore.
See also bug 5977 which notes that closed bugs are not visible in a persons related bugs pages.
affects: | launchpad-foundations → launchpad-registry |
affects: | launchpad-registry → malone |
summary: |
- Launchpad bug seemingly disappears when marked as duplicate + Person's related bug pages hides duplicates |
description: | updated |
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: bug-search |
I don't consider this of low priority. I ran into the very same problem for my report of bug #806094 and was more than baffled when there suddenly was *no way whatsoever* to find *my own* bug report other than find the report it was marked as a duplicate of. And since this report had completely different title and keywords, the connection is basically lost. This problem would be mitigated of bug #30307 was solved.
In the end the only way to find my bug report was searching my launchpad emails and finding the one I had received after originally reporting the bug. Had I deleted these emails, I would never have found my bug report again. This needs urgent fixing and should be given high or critical priority.