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

Transition field-based rule not working

I have a workflow where I want to make a the ability to make transition be conditioned on the values of two different fields. For that, I've added two field rules to the transitions. However, only the first of these two is actually working, since the second rule is not blocking anything when the condition is not met. I am attaching screenshots of the evidence, including the rules set and the example of the ticket.

2 answers

attached now, as you see, the value for this particular ticket in 'has comms release' is 'No' but they're still able to make a transition that requires it to be 'Yes'.

0 votes
John Funk Community Leader Aug 01, 2022

Hi Sergio,

I don't see any screenshot attached. Can you try to add that again? 

John Funk Community Leader Aug 02, 2022

You have two rules on that transition. It will check the first and if it passes, it will the issue go. It implements the rules as an OR not an AND. 

huh, that seems like a major flaw, one would assume these are treated as AND and not OR

John Funk Community Leader Aug 02, 2022

Agreed - but it is what it is. You can reverse them to try it to see if it behaves differently. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events