[haiku-development] Re: Altering Trac's ticket workflow
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 23 Dec 2009 12:16:39 +0100
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?
> > IMHO, the ticket state that is actually (additionally) missing is "working
> > on it", so that "accepted" could be used for what it is probably meant,
> > which is accepting responsibility for the ticket without implying that the
> > ticket is now being working on.
>
> Okay, so if I understand correctly you think you need to be able to
> signal that a ticket belongs in you area of expertise, but without
> actually saying you are going to work on it directly (thus leaving it
> open for others to chip in before you).
Yep. Though I'm only saying that it would be missing for clarity, not that we
really need it. The current workflow works well enough for me.
> 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.
> Nonetheless, for clarity purposes it is entirely possible to introduce
> the 'working-on-it' stage! I'm neutral to this point.
I'm not passionate about it either. Though I think, it would be good to at
least rename the current "assigned" (i.e. future "accepted") state to
"working on it", since that's how we're currently using it.
CU, Ingo
Other related posts:
