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

[Edward Welbourne]

Hi all,

We currently have an "In Progress" state.  In practice when I work on an
issue, I initially do the work, then put that up for review; the review
phase takes up fragments of my time for a while, unlike the main work
phase, which is closer to full-time.  I have more control over (and a
better ability to estimate) how long the actual work takes, while review
(and subsequent integration) depends on factors outside my control, that
are harder to estimate.

(Sometimes, under the present branching model, I also have to put work
on hold until other work merges up for me to rebase it onto.  However,
that complication shall go away soon, so I'll ignore it.)

When my team is planning sprints, our scrum master wants to know what
tasks I'll be working on, and what counts as "Done" for each of them.
Having a separate state for "In Review", distinct from "In Progress",
would let us distinguish the relatively plannable, and intense, part of
the work from the part that (often happens in a later sprint, and)
takes up a smaller proportion of my time but may take longer.

So I'd like to modify our Jira work-flows to include a distinct "In
Review" state for when I've completed the main work and am either
waiting for review or responding to reviewers' comments.  Of course, if
those comments prompt me to go back and start over, I'll also want to be
able to go back to the "In Progress" state from it.

Does anyone have any objection to this, or suggestions for a better way
to handle the relevant work-flow transition ?  If not, I'm hoping Alex
can work out how to implement what I want ...

	Eddy.