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

Multiple IF statements that are not mutually exclusive


I have created a checkbox customfield where multiple options can be selected. I have tried to create an automation rule that checks for each options if it is selected, and if so creates a specific issue (see below). 

Now In the below example, if I select both 'UK' and 'ES' cultures, both issues are created. But if I only select the second option (ES), nothing happens as the automation does not get past the first validation. It must be because these IF statements are actually nested and not validated separately. If it doesn't pass the first IF, the second is never reached. This forces me to create separate automation rules per culture. Is there anything that I can do to perform this automation in a single rule?

Mutliple IF statements.png

2 answers

1 accepted

14 votes
Answer accepted

Hi, @Ivo_de_Vries -

I just encountered a similar issue while working for a customer.  My co-workers and I figured out that if you embed each separate If statement in a Branch, they will all be validated separately.  Here's what we came up with:


I hope that helps you (belatedly).

This is perfect!  This worked for me, and I believe this would help the OP in the situation they were having.  This solution should be at the top.

Thanks @David VanDyke that helped me

Fantastic!  This has been annoying me for hours.  It's so annoying that when an IF is true it ignores all the others :/

Hi Ivo,

I'm Ilenice, from Automation for JIRA Support team.

Thanks for your question!

Well, what is happening to your rule is that, since “ES” option is selected, the first JQL condition doesn’t match, and then the rule stops executing, not even checking the next condition.

To your use case, I would suggest you use an IF/ELSE block condition:


You can configure your two JQL conditions inside this IF/ELSE block condition. I’ll show you how.

Please set your rule using the structure described below:

  • TRIGGER - When issue transitioned;
    1. IF BLOCK
      • JQL Condition, setting the expression issuetype = "Communication Request" AND "Type of Communication" = "Urgent communication" AND Cultures = UK
      • CREATE ISSUE action
      • JQL Condition, setting the expression issuetype = "Communication Request" AND "Type of Communication" = "Urgent communication" AND Cultures = ES
      • CREATE ISSUE action

It’ll look like the following:



So, please note that when using an IF/ELSE block condition, if the first condition doesn’t match, Automation will check the next condition. :)

I hope it helps!

Let me know if there is anything else I can help with.



Hi Ilenice,

Thanks for your elaborate and quick answer. This also is not a solution for the current use case as the IFs are not mutually exclusive, I will explain a bit more on the context and the current (not ideal) workaround I have for it.

Our company serves about 18 countries and whenever we send out a communication, an issue of this type is created first. Whilst creating the issue, the cultures are selected that the communication applies to. Per culture that is selected, I want to generate a ticket for that specific department to handle the translation and sending of the communication. On the creation screen, the reporter also selects one of the predefined 'e-mail templates'. 

Ideally, I would like to create a single automation rule per e-mail template, with an IF for every culture. IF checkbox culture is selected for UK, ES, NL and FR, the automation rule should create 4 issues respectively for each country. Using multiple IF's or an IF/Else structure does currently not work as explained above. 

I would like to have a single automation rule per e-mail template as it is much more efficient to copy a rule for a new template (with all the IFs per culture) each time we introduce a new one (and make small adjustments to it). Currently my workaround is not to create automation rules per template but per culture (18 rules). Every time a new template will be added, I will have to add another IF statement to each of the 18 rules.

Hi Ivo,

thanks for replying and I’m sorry for my late response.

I’ve discussed this point with the dev team and, unfortunately, at the moment it’s not possible to achieve the result you want at the moment. For now, it indeed demands you to configure the 18 conditions, that is, one condition to each country available on the checkbox field. 

However, through AUT-81 (You may need to open in an incognito window) we’ve been tracking an improvement which could help you on this, so we might have good news in the future. :)

In case you have any other questions or doubts, please feel free to make a new contact.



Like Ivo_de_Vries likes this


Do you know why i cant see if-else block while adding new component condition in Branch rule in second screen shot with red pen?


sc-1 with if-else block.PNGsc-1 without if-else block.PNG

Hi, @Milan Ardeshana!

Yes, you're right, this is indeed not available. :(

By now, it was restricted to prevent performance issues.

There's an AUT raised for this, through which this point is being tracked: - you might need to open this on incognito.

Let me know if there is anything else I can help with.



Like Milan Ardeshana likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events