nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

If/Then not available in sub-tasks?

MJCorcoran

I have an automation (below) and I would like to use if/then statements to have a different action/sub-task created depending on the value of an issue field (Middle Name). I cannot get it to run at all if the 1st If statement (that it's not "Enter Middle Name" or "NA") fails. Normally, I would use an If/Then/Else block, but it seems that I'm using some kind of limited automation rule where the options for branching are limited, or am I missing something obvious?

Jira Pic.PNG

Accepted answers

Bill Sheboy

Hi @MJCorcoran

You appear to be branching on current issue; that is not needed if your intent is only to work with the current issue (i.e., trigger issue in your case).

After you remove that branch, you may use the if/else conditions as they will not be under a branch.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @MJCorcoran

You appear to be branching on current issue; that is not needed if your intent is only to work with the current issue (i.e., trigger issue in your case).

After you remove that branch, you may use the if/else conditions as they will not be under a branch.

Kind regards,
Bill

Mohanraj Thangamuthu

Hi, could you try automation shown on the image below.

Screenshot 2023-07-19 at 11.19.46 AM.png

MJCorcoran

I actually double-branched and it work great. I tried using a variable, but it didn't work well.

Bill Sheboy

Well done! And an FYI...

When using branches in automation rules, scope is important...particularly with issues and created variables.

Specifically: branches on one-and-only-one issue get run in-line (e.g., branch on current issue, branch on parent, etc.), as if the branch was not there. All other branches run in-parallel and asynchronously. And there is no guarantee when such branches will complete...right up to the last step of the rule.

The impact of this is if you create a variable inside of a branch, the value is usually not available outside of the branch. (This is because the variable is re-created and goes out of scope with each loop.)

So, for the first case (i.e., one-and-only-one issue branches) created variables can be preserved using a "trick"/feature of such branches:

action: create a variable, with the name varMyVariable
branch: on current issue
- some actions...
- action: create a variable, with the same name varMyVariable
- ...
outside of the branch, the variable has the updated value AND still exists

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management