How to construct multiple If conditions to be executed if value is found in Jira Automation Rule?

[Jar Lady]

I want to have a rule that executes in this manner:

-   If field A is not empty

    Do AAA

    If field B is not empty

    Do BBB

    If field C is not empty

    Do CCC

So if all A, B and C fields are not empty, I will expect to have done AAA and BBB and CCC.

Currently I configured in the above manner in the Jira automation rule, but the rule did not execute further of "If field C is not empty" if let's say field B is empty. Is there any example to show the correct configuration?

[John Funk · Accepted solution]

Hi Lady,

Since you want all 3 to execute every time, no matter if one is empty or not, you will need to use Branches Use a  Current Issue Branch for each thing to check, then put a Condition under the branch for each item you are checking. Then put under the Condition and Action for what you want it to do if it passes. 

The good thing is that you can create the first branch and all the details, then Copy the branch and just make changes to the Condition and Action for B. Then Copy that one and do the same for C. 

However, these will not fire sequentially, but all at the same time more or less. 

[Jar Lady]

Oh thank you, let me try it. How do I copy a branch? 

[Jar Lady]

Thank u! Prob solved using current branch.

[Jar Lady]

Thank u!

[John Funk]

If you hover over the branch, you will see a little popup like in the image below. Click on the copy icon. 

[Jar Lady]

Thank u!

[Bill Sheboy]

Hi @Jar Lady 

Would you please describe the problem you are trying to solve?  That may help the community to offer suggestions, because...

In rules, branches cannot be nested and if / else conditions cannot be defined inside of branches.  And so the scenario you described may not be possible with a single rule:

While iterating over the linked issues,
Perform several different and independent conditions, 
Each of which can produce a different action.

And...if the branch on linked issues was repeated (to allow performing the actions separately) that may not work: branches which could be on more than one thing are run in parallel and asynchronous processing, leading to update collisions for the rule actions on the same issues.

This may be possible if there is a way to make the issue selection distinct with JQL, although that will lead to 2^3 = 8 path branches, using JQL to select the issues.  For example:

• if A and B and C are empty, the first branch processes
• if A and B are empty, and C is not, the second branch processes
• ...
• if A and B and C are not empty, the eighth branch processes

Kind regards,
Bill

[Barker]

thanks for sharing. Office ally  i will also tray this