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!


Conditional Workflow Transitions

Hi all

There are some things I'd like to do as part of my JIRA flow but I can't figure out how to accomplish this (I am a Business Analyst and only a JIRA project admin so can't play with the settings myself).  My admin has put it in the too hard basket so I'm trying to, with your help, put together concise instructions to find a solution.


Firstly, I have created a document approval workflow which looks like this:

  1. Documents requiring edit are placed into individual tickets in 'To Do' status
  2. A person edits a document and transitions to 'Ready for Test'.  Automation makes this person the 'Editor' which is a custom person field.
  3. A person then tests, it can be rejected and automatically assigned back to the Editor (via automation) but if approved, it's marked as Done and this person is set as the 'Tester' which again is a custom person field.

This is a small team so anybody can edit and anybody can test, but a person cannot do both.  How can I build a conditional workflow so that if Current User = Developer then they cannot mark as Done, please?

Looking through the JIRA options I see a 'Value Field' condition but this is not constant so unsure if my use case can be dealt with?  

I also see there is a 'Separation of Duties condition' however given the flow can go back and forth, would this rule work?

I'm open to any ideas please, perhaps look at approvers rather than such a custom setup? 


Secondly, although document edits follow the above process, there is a shorter and more simple process for document archiving.  This is what I imagine it would look like to a user.

  1. Documents requiring archival are placed into individual tickets in 'To Do' status (same as above) with component 'archive' added
  2. The only transition option visible should be 'Pending Archive' rather than 'Ready for Test'. On the flip side, with the normal process above where the component 'archive' does not exist then the only visible transition should be 'Ready for Test'
  3. Once confirmation of archive is received, this would then transition to 'Done'

I am unsure of the best method to have a conditional workflow off to the side of my current flow.

Thanks in advance for reading my problem and extra thanks if you can attempt to help me.

Have a great day, Brendan


1 answer

Hello @Brendan Sheppard

For document approval workflow V1.2,

The Jira admin can add a Condition to the transition to Done.

Select "User Is In Any Project Role" or "User Is In Any GroupCondition to allow only users in a given project role/group to execute a transition.

Then only allow QAs to move to Done.

Configure advanced issue workflows


Yes, I would create a separate workflow for Archiving.

Project can have multiple workflow

Thanks for your reply LynnG

As mentioned, we don't have the concept of developer and QA teams, any person can develop or test, but that person cannot do both.  Therefore, I don't believe this solution works.

That link gives me a 404 error.

I solved my second query by adding a label to the tickets with the different flow and utilising automation to branch.

Like LynnG likes this

I'm glad that you solved the problem @Brendan Sheppard 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events