You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2012/09/03 12:50:30 UTC
Re: [Apache Bloodhound] #194: Examine workflow for Bloodhound site
#194: Examine workflow for Bloodhound site
------------------------+--------------------
Reporter: gjm | Owner: nobody
Type: task | Status: new
Priority: major | Milestone:
Component: siteadmin | Version:
Resolution: | Keywords:
------------------------+--------------------
Comment (by jdreimann):
Replying to [comment:6 olemis]:
> Replying to [comment:1 jdreimann]:
> > I can think of a few things that could help here, some immediate, some
longer term:
> I welcome all these suggestions, yes . Especially sometimes it's a bit
hard for me to determine assigned tickets having pending patches , for
instance .
I agree. My suggestion for this is the 'pending review' status.
> > 2. The status of tickets is currently either 'new', 'assigned',
'accepted' or 'resolved' and 're-opened' as far as I can tell. In reality
something like this happens: 'new', 'work in progress', 'pending review',
'resolved'. (Work usually means code). Matching this more closely and
providing better control to move between states would help.
>
> The only thing I'd like to add is that sometimes between 'work in
progress', and 'pending review' , ticket enters an state in which nothing
can be done until something happens
Your examples describe a blocker issue in my opinion, some internal and
some 3rd party. Internal means the ticket that is blocking progress should
be changed to 'blocker', external means we should add a ticket type that
is 'External' or '3rd party' and assign it a 'blocker' status if it's a
blocker.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/194#comment:7>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker