Hello David, thanks for your report!

The first few versions of DebGTD behaved in the way you
expect: all non-asleep, non-ignored bugs were displayed
in the main GtkTreeView.

However, in July 2008 the 'Triage' window was added. From
that point onwards, the main TreeView only displays bugs
that are also triaged.

The reasoning is thus: every bug is like a "TODO" item, and
you need to know what the next action is for each todo item
before you can reasonably prioritise them. The way that the
triage window works (showing you bugs one at a time, not
letting you choose an order) is also on purpose: if you
need to decide on a next action for every bug, attempting
to sort the list in any way is a distraction from the task
at hand.

One thing I have been intending to do but haven't managed
yet is to switch out the TreeView with a label (or similar)
when you have no triaged bugs, explaining that you need to
triage bugs to have them appear in the list.

The rule of thumb should be something like this: for each
bug, if you can complete the bug in under two minutes, do
so, otherwise, record what the next action on the bug needs
to be (such as: confirm this still happens, check to see if
it's reported upstream, etc.) and move onto the next bug.

This was a fairly big change from the previous behaviour
and DebGTD as it stands is fairly incomplete. I'm not sure
what the best thing to do is once you have finished
triaging, for example: is a sortable list of open bugs
really the best way to proceed? (I suspect that sorting on
"next action" would be useful if e.g. you wanted to do a
batch of "confirm this still happens"-style work in one
go...)

DebGTD is really an experiment, trying to explore the best
workflow for a bug reporter. As such, I am open to
suggestions from people who have tried it and can think of
ways it should be improved: if it was just for me, there
would have been no point in uploading it :-) So based on
what I've written here, I'd love to know what you think of
this flow and where it might be improved.


Thanks,

-- 
Jon Dowland

Attachment: signature.asc
Description: Digital signature

Reply via email to