Any way to individually track & prioritize bugs?
I've reported and/or commented on more than a few bugs in launchpad (and Debian, and GNOME, and... etc.). Because I have so many open bugs, YET I often can't spend much time on this, I have my email program filter all bug-related emails into a folder. SO I get so many notification messages, the ones I want to track closely get lost. Unfortunately it has usually been months since I reported the bug and I can't tell from the email whether this a bug I reported or one I was tracking for some other reason, and if I'm rushed I don't follow the link back to launchpad to see who the question is directed to. OR there has been some sort of bug activity and my email program "collapses" all subsequent messages into a "discussion" under the first innocuous heading and I miss seeing a later message with pertinent information. SO I often miss activity and requests for more information that are directed to me.
It would be really great if Launchpad included a way to individually track a bug's status from my perspective -- as a To Do list, "unread bugs," and some other way to personally prioritize the bugs. I especially need to mark them somehow when there's a request to ME for more information that I need to research. Launchpad doesn't show when I've looked at a bug report, so I can't tell at a glance (from Launchpad) that I've missed some recent activity. (If the status is "needs info" then I should look at it, but again that requires me to evaluate whether the "needs info" is directed to me or someone else.)
I'd like to be able to go to a page in Launchpad and see the bugs that _I_ consider myself to be working on, maybe ones that I have myself flagged for my personal follow-up (and/or that others have flagged on my behalf). It might also be a place where I could have a scratchpad of things I want to remember but might not be useful for the public reports.
I have considered using my personal wiki page to making links to the bugs I am working on, but of course I would have to manually mark any changes in bug status.
I'm a very part-time user, but I have to think heavy launchpad users have similar issues. What techniques do the "pros" use to keep track of multiple open bug reports?
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask Tommy Trussell for more information if necessary.