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

  • From: Niels Reedijk <niels.reedijk@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 23 Dec 2009 13:23:55 +0100


2009/12/23 Ingo Weinhold <ingo_weinhold@xxxxxx>:
> On 2009-12-22 at 19:55:37 [+0100], Niels Reedijk <niels.reedijk@xxxxxxxxx>
> wrote:
>> > Given how we currently use the "accepted" state (which is currently named
>> > "assigned" -- namely as "working on it" -- I think the only thing that
>> > will
>> > change by introducing the new ticket state, is that there'll be three
>> > states instead of two a ticket can be sitting in while waiting for being
>> > worked on:
>> >
>> > * new: Assigned via component owner.
>> > * reopened: Formerly closed.
>> > * assigned: Assigned via triaging.
>> Correct.
> Mmh, but then I don't see how that would help with triaging. Or would you
> also process and (re-)assign new tickets that already have an owner?

Eventually, if it turns out that we are able to have a good team of
triagers, I would say that our effort would be to have the triagers go
through all new tickets to check out whether they pass the criteria
for a good bug report before a developer spends time on it. This of
course depends on the wishes of a component owner as well.

>> I would say leaving a ticket
>> in the 'assigned' state (perhaps with a short acknowledging comment)
> OK, then I probably misunderstood an aspect of what you intend to achieve
> with the new "assigned" state. I thought it was also about being able to
> quickly get an overview of the tickets that haven't reached their "final
> destination" yet, i.e. the developer that feels responsible.

Actually, you are right. The assigned state implies two different
things, either the ticket is still on its way to a final owner (who
will then accept it), or it might be at the right owner already, but
he is not working on the ticket.

In any way it means that the ticket is up for grabs for anyone that
wants to do it, whereas the 'accepted' state implies that the ticket
is already being worked on.

As it is not possible to have spaces in status names, the status could
be 'working-on-it' or 'in-progress'. Personally, I find the name
'accepted' clear enough, it is a matter of convention, but
'working-on-it' certainly is more intuitive.

I propose changing the ticket workflow and see how it works. The
system is quite flexible and we can tweak it along the way if it turns
out to be needed. (Mind that I don't mean to say that we should be
tweaking it daily or weekly though).


Other related posts: