JIRA WORKFLOW Multi-validation

Hi all,

I would like to make a workflow with a specific attribute. It should be able to pass to the next status only if two statuses are validated.

If it's not really clear, it will certainly be clearer with a schema :

 

It will must wait the first validation and the second validation to pass to "Analysed" status.

Workflow - JIRA.PNG

4 answers

1 accepted

1 vote
Accepted answer

Done

Why not have your flow go Submitted - Validator 1 -(transition with validation) - Validator 2 -(transition with validation) - Analyzed?

It can only be in one status at the time anyway?

It's better (for validators) if it's two different transitions from the same status..

You can do it like this:

1) Replace the names of the status with "VALIDATED BY 1" and "VALIDATED BY 2". This is only to make clear that each status means that the issue has been validated by one of the 2 possible validators.

2) Transition from "SUBMITTED" to "VALIDATED BY 1" should have a condition that ensures that it can only be seen (thus executed) by validator 1, and transition from "SUBMITTED" to "VALIDATED BY 2" should have another condition to ensure that it can only be seen by validator 2. I recommend you to use two different project roles for implementing the conditions.

3) Transition from "VALIDATED BY 1" to "ANALYSED" should have a condition that ensures that it can only be seen (thus executed) by validator 2, and transition from "VALIDATED BY 2" to "ANALYSED" should have another condition to ensure that it can only be seen by validator 1. Note that here the conditions are twisted in respect to previous transition.

This way you will ensure that both validations have been carried out before reaches ANALYSED status, but you allow to do them in any order.

More complex scenarios are also possible, like this multi-approval solution implemented using JIRA Workflow Toolbox plugin.

Thank you for your answer. I'll try this tomorrow !

What is different for each status? A different screen - custom fields to complete?

No, the permissions are differents

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,352 views 14 19
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you