[haiku-development] Re: Altering Trac's ticket workflow

  • From: Niels Reedijk <niels.reedijk@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Fri, 18 Dec 2009 09:44:46 +0100

Okay, trying to finish this thread.

1. Is it clear how this Trac 0.11 workflow differs from the workflow
we currently have?

In short: this workflow allows us to identify 'untriaged' bug reports
by adding a status called 'accepted.' Currently, in theory we can
currently do this by looking at the tickets with status 'new' and
assignee 'nobody', but some components have a default owner and that
means that the 'new' tickets will already have an assignee.

To address this, a new level 'assigned' will be added, which will be
set when a ticket has been triaged and then redirected to an owner. It
is then under the responsibility of that owner to assign it to someone
else, or to accept it (setting the status to accepted).

2. What will happen to me if I am a developer?

Nothing really. If you own a component, you will still get notified if
new tickets arrive in your component. If the ticket belongs to you,
you can 'accept' the ticket. Instead of that the status will be
'assigned', it will be set to 'accepted'. There are no extra steps
involved, it is only the internal accounting that will change.

So in short: this change in the workflow does not create extra steps
or extra overhead, it just adds a minor change in the workflow and a
new status. After the change is implemented, I am going to see whether
it is feasible to organize some sort of triaging to see whether we can
produce better tickets before they end up on the desk of the

So, is this an acceptable change?


Other related posts: