Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Workflow Validation to send issues down specific path of workflow

I have a new change management workflow that was given to me to build. It has three sections or paths to flow from. I want to use validation to move specific issues down the workflow. Is this possible to do this without an add on or automation with in the workflow?



1 comment

Benjamin Community Leader May 05, 2020

@Aaron Geister - The next step in the workflow is driven by your transition. Validation is used to just validate your issue that it has meet some rules to make it to the next status in your workflow. 

Two ideas out of the box:

1. Allow the end user to chose where the change management goes by creating 3 transition to choose from. 


2. Create 3 different change management issues if they are completely 3 different kinds of workflows. 

This is what I was trying to tell my team but they want this big all in one workflow so they will have to choose to which transition each issue type will flow. Thanks for your help.

Benjamin Community Leader May 07, 2020

@Aaron Geister - You welcome. That is possible out of the box. Not recommended. Let's say you are open or todo state as your starting state. You can add however many transition you want to go through another path. 


For example, for simplicity, you can have a transition to go to next status A1 and another to B1 and and another too C1. 

@Benjamin Yes exactly what I have been building.  Here is a look to what workflow was given to me to build for change management. I have never built one so big as to me straight to the point would be better but this is what the change managemen process group wants. 


Benjamin Community Leader May 08, 2020

As long as it's agreed by the key stakeholders as the solution and meets their requirements, then move forward. The good thing is Jira allows the flexibility. However, just be aware of the maintenance. There's probably some areas to simplify as possible like two validate and implementation state. 

I agree with you and I have already compressed what they wanted and thought we could even compress it more. 


Log in or Sign up to comment

Atlassian Community Events