Automation for Jira - Logical OR statement within an IF block

[Malka]

I have three fields: 

1. Release Notes Required
   1. Both
   2. Internal
   3. External
2. Internal Release Notes
3. External Release Notes

Based on the answer selected on field 1, I want to check the population of fields 2 and 3. So if Both is selected in field 1, I want to check if either 2 or 3 is empty and generate an alert. Where are the ORs in Automation for Jira?

[Mykenna Cepek · Accepted solution]

It's not the most intuitive approach, but this might work for you...

Try using a "Branch rule / related issues" component instead of a "New condition" component.

Start with a "Branch rule", and for "Type of related issues" select "JQL".

Your JQL could be:

"Release Notes Required" in ("Both", "Internal")

for the first clause, performing the desired internal operations in that branch clause.

At the same level you can use another branch with JQL:

"Release Notes Required" in ("Both", "External")

for the second clause, performing the desired external operations.

An alternative is to use a single "If/else block" conditional like this (using pseudocode):

If "Release Notes Required" = "Internal"
Then DoInternalStuff
ElseIf "Release Notes Required" = "External"
Then DoExternalStuff
Else
DoInternalStuff
DoExternalStuff

I hate duplicating stuff, so I don't like that approach as much.

Do share back here with what worked for you! 

[Mykenna Cepek]

OPTION 1:  Some OR conditional functionality is built-in to some conditionals. Example: "is one of" option in the "Issue fields condition". That can check, for example, if the Assignee is Mary or Bob.

OPTION 2:  When there is no built-in support, the smart value or() function provides a messy but functional alternative:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/#or

Sample use case:  A rule triggers on a new Comment added to an issue, and I want to proceed only if it was Mary or Bob who added the comment. The "Issue fields condition" doesn't provide access to the comment author (it's not a standard or custom field for an issue).

So I'll use a "Smart values condition" instead:
 

It's a bit brittle, as the user name is in text form (whereas the OPTION 1 approach above relies on user ID values internally).

You could check against just comment.author if you knew the user ID value, but that would make your rule much less readable -- my Cloud user ID is 43 characters of nonsense.

[Mykenna Cepek]

I noticed that the "If/then/else" conditional in Jira Cloud now has an option for AND vs OR with the configured conditions:

[Evan Aronson]

There is a workaround for "Advanced If" described here:

https://community.atlassian.com/t5/Jira-questions/automation-Advanced-compare-quot-or-quot-condition/qaq-p/1815711

[Bill Sheboy]

Hi @Malka 

I don't see any OR conditions... Only AND using sequential condition tests.

Have you tried something like a trigger on a change to the Release Notes Required field, and then use either a JQL condition containing an OR clause, or If/Else to send the alert you want?  The If/Else may be better for your case, and faster too.

Best regards,

Bill

[Malka]

Thought about that, but it would require them completing 2 and/ or 3 prior to 1. 

That's why I'm leaning towards the check at time of transition. Oh aaand ro make it more fun, I'm checking these three fields in a parent of the transitioning issue. 

[Bill Sheboy]

Gotcha; so this depends upon the level to which you want to nag...I mean alert...someone.  As the sub-task is the item changing, it doesn't matter the conditions of the parent's fields; you just want to alert about missing data, correct?

You might need a triggered rule on the sub-task, and either a manual or scheduled rule for re-check. (Or better still, a filter subscription independent of the rule.)  If you want to limit the alerts, you could flag a comment after someone has been notified, and check for it as a condition to prevent re-alerting.

• Trigger: sub-task transitions from status-A to status-B (or whatever you are choosing)
• Branch: parent of sub-task
• Condition: If/else for your number of alerting scenarios
• Action: email, comment, etc. to alert

[Anand Inamdar_Amoeboids]

From my limited knowledge of Automation for Jira, it does not look like what you are trying to do is easily achieved (if at all possible).

Do share the solution here if you find a way do it.

Best,
Anand

[Malka]

Thank you for your product's advertisement but it does nothing to solve the issue I am having. 

[Anand Inamdar_Amoeboids]

My apologies if that came across as an advertisement of sorts. I've just removed that part from my response. 

Would still love to know the solution if you find one that relies on Automation for Jira.

Best,
Anand