[Development] Proposal: more Jira states to track stages of the work on an issue

[André Pönitz]

On Tue, Feb 18, 2020 at 01:11:29PM +1000, Lorn Potter wrote:
> On 18/2/20 6:03 AM, Thiago Macieira wrote:
> > I'm with Alexandru here: all ideas to have more states in JIRA start with a
> > good intentions, but eventually people stop using them and just transition
> > through all stages in one go when they've finished the work. For example,
> > people realise they've never changed from Reported to Confirmed before they
> > actually submitted the fix and autotest to Gerrit. I often do that and the
> > task goes from Reported to Confirmed to In Progress in 5 seconds. With your
> > proposal, it would go through yet another state in that period.
> 
> Stepping through the interim steps is not a requirement, so it is not that
> much difference to go from Reported->In Progress to Reported->In Review,
> really.
> 
> So the list you have to select from has one more entry to choose from, is
> that such a big deal?

This is not the problem.

More states lead to bikeshedding what would be The Right State for a task.

Already now there are tasks that get prioritized, and assigned, and
re-prioritized, re-assigned, "Fix-for-version"-ed, closed, re-opened
several times. Watchers that e.g. wait for a "Done" there get notified
each time on such unprogressing transitions, and skipping these sums
up to quite a bit of unproductive time already now.

> > What's the harm in leaving the task in In Progress state while it's being
> > reviewed?
> 
> There is no harm, but being able to better distinguish the main development
> phase of a large task from the review stage would benefit the 'pointy hairs'
> [...]

Looks like we are getting to the actual problem here. It's not about
development after all.


Andre'