Add an "In Review" state to JIRA?

[James Dumay]

Hi all,

Blue Ocean had previously had an "In Review" state in JIRA to track which changes are in development but are ready for review as a PR when we had these tickets in a private JIRA. 

The developers working on Blue Ocean would like to introduce it again so we  have a more accurate state for where each other's work is at. For the design work the In Review state means that a design is "ready enough" (proposed, rather than just spitballing) to receive input from the wider community. In that last case we would be using this status to facilitate feedback on UX with the community.

Would there be any objections to adding this to the JENKINS project's JIRA workflow? There should be minimal/no impact for other users.

Request is being tracked on https://issues.jenkins-ci.org/browse/INFRA-802  

Thanks,

James

[Daniel Beck]

How would the workflow change? I.e. what state transitions will be added/removed?

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/96ed51c5-dd8c-4090-8723-3bc226c04c20%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[James Dumay]

You would just get an additional optional "In Review" transition. Everything else would be the same.

[Michael Neale]

Given that most tickets/changes spend some time in PR-review state, this is exactly what in-review is for, so no real change for anyone.

They can choose to place an issue "in review" to save people thinking that there is still code being written for it (or they can leave it as is). 

On Friday, July 1, 2016 at 9:42:43 PM UTC+10, Daniel Beck wrote:

[Ulli Hafner]

A transition for each existing state? 

And which transitions are available for the new state?

It might help to see the output of the state diagram of the corresponding Jira instances.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/90404d4d-4bb3-4b6e-a629-50a2c00654ea%40googlegroups.com.

[R. Tyler Croy]

(replies inline)

On Mon, 04 Jul 2016, Ulli Hafner wrote:

> A transition for each existing state?
> And which transitions are available for the new state?

Our JIRA workflow is kind of silly as is, but here you go :)

<http://imgur.com/a/dZhGc>


- R. Tyler Croy

------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>

% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
------------------------------------------------------

[Daniel Beck]

> On 07.07.2016, at 21:57, R. Tyler Croy <ty...@monkeypox.org> wrote:
>
> <http://imgur.com/a/dZhGc>

Is one of the 'Start Review' supposed to be 'Stop Review'?

[James Dumay]

@daniel - yes, looks like an error.

Any major objections?

[Daniel Beck]

> On 08.07.2016, at 02:59, James Dumay <jdu...@cloudbees.com> wrote:
>
> Any major objections?
>

To clarify, I can go from…

In Review -> Open
Open -> In Review

In Review -> In Progress
In Progress -> In Review

In Review -> Resolved

Is that correct? The visualization is not entirely clear.

[Ulli Hafner]

You then should also add the two review transitions (in and out) to reopened.

Is the verified state required? I think it could be removed.

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/D09E99F8-4194-47DE-A3E8-E83BA4F65255%40beckweb.net.

[Ulli Hafner]

Am 08.07.2016 um 02:59 schrieb James Dumay <jdu...@cloudbees.com>:

@daniel - yes, looks like an error.

Any major objections?

No, I think it is no big difference for the non-blue-ocean developers.

(But I think you should check on your own in a couple of weeks if the new state really helps you in your development process. From a lot of other projects I have the experience that such states (that duplicate work) will not be used with the same enthusiasm after a while)

On Friday, July 8, 2016 at 7:01:47 AM UTC+10, Daniel Beck wrote:

> On 07.07.2016, at 21:57, R. Tyler Croy <ty...@monkeypox.org> wrote:
>
>    <http://imgur.com/a/dZhGc>

Is one of the 'Start Review' supposed to be 'Stop Review'?

--

You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/70e4b2c2-795e-45c3-9806-8e6dbe33923b%40googlegroups.com.

[Thorsten Scherler]

Hi all, 

I am not 100% but I believe you can have kanban or scrum dashboards on a project level. Meaning we could limit it to only the blueocean dashboard.

salu2 

[Jesse Glick]

On Thu, Jun 30, 2016 at 6:39 PM, James Dumay <jdu...@cloudbees.com> wrote:
> There should be minimal/no impact for other users.

Well, if such a state were available, I for one would use it
elsewhere. For our internal JIRA we have such a state and it is useful
to indicate that there is a PR filed for the issue, and I as the
developer consider the work done unless someone objects to the PR, so
we are are just waiting for some positive reviews followed by merge
and release. If the reviews are negative and demand significant
rework, then it goes back to In Progress.

[Stephen Connolly]

+1 (and same jira. it has been very helpful for us)

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1d%3DNYwLa%3DD255ppm5jYQc4%3D%3Dx9DX%2ByBK1r1ivOwHcAOw%40mail.gmail.com.

[Thorsten Scherler]

Yeah, I admit it is really helpful to indicate "I think it is ready, do you?" as you describe Jesse.

salu2

[James Dumay]

Uli we used this status to great effect on our JIRA before we moved the project into OSS - so I believe we will be happy to have it back :)

If it causes any detriment to other project members we can re-evaluate it again.