Recently I wrote a piece of software to help me manage my Debian bug workflow called debgtd. At the time I announced it, debgtd did little more than display a list of bugs you have submitted, let you remove some entries from the list and sort them by severity or package name. This is the version that will be in Lenny.
Being able to work through a list and bin things that do not need your attention is important, but it's only one part of the "triage" process. According to David Allen's GTD philosophy, what you really need to do is establish what the next action for each bugs needs to be. (In the case of bugs we bin, nothing).
The versions of debgtd since the lenny release feature two major differences:
the main view now only displays bugs which have a "next action" defined -- which, for new bugs, is none of them.
A "Triage" window has been introduced.
the new triage window
The new triage window presents one bug to you at a time and lets you either sleep, ignore or provide a next action for the bug. (Or close the triage window).
For the triage window, I've purposefully not sorted the bugs in any way. The idea is, you should be able to decide the next action (or to bin the bug) in a minute or less per bug. You need to triage every bug, so sorting them does not achieve much, and perhaps distracts from triaging them adequately.
I am now in a position where I can sit down and define a next action for myself for all of the 100 or so bugs I have reported in a short amount of time, and then present those bugs and their next actions in a list form.
Still to do before I make this post "public" is to thaw bugs after an amount of time.