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 statement works / identical branch fails

Diane Fahr

I have an if statement that has two conditions:

a field check and a related issue condition checking if a JQL condition is present .. the if is successful (which is what I would expect).

within that if, I have a branch - the branch branches on the exact same JQL condition from the if and fails with "No related issues could be found.". If i log the JQL issue and search on it, the issue is found.

thoughts on why this might happen? diane

Accepted answers

All comments

Trudy P Claspill

Hello @Diane Fahr

Whenever you ask for help with an Automation rule, it will enable us to help you more effectively if you provide screen images that show the full automation rule, the details of each step, and the output from the rule execution audit log.

Diane Fahr

@Trudy P ClaspillThank you Trudy, I have attached the flow that is failing (sometimes) - here is the flow -

1. a new initiative is created and during this creation a squad story and sub-tasks are created.
2. a custom field is set which in turn triggers this automation
a. the if condition is (add a new squad, and if the squad story exists, but a specific sub-task does not exist - then take this leg. (this always passes the first pass).
3. a new squad is added to the initiative and their story / sub-tasks are created.
4. since the custom field is already set this automation runs again.
5. the if statement passes (as expected) however the identical branch fails on the second pass with:

Branch rule / related issues

No related issues could be found.

You might be able to convince me of a timing issue, but I would think if that were the case the initial if would have failed. The first branch (which renames an existing sub-task, and the second branch that creates the new sub-task) can execute at the same time.

So, let me throw in some mud ..

first pass - if and rename branch and create branch work (regardless of how many squads we start out with)
second pass - new squad - if and rename branch work - create branch fails
third pass - add new squad - if and rename branch work as before - create processes the story that failed in step 2 .

after that, consistency for create branch is .. inconsistent (or i am still struggling to find a repeatable pattern) atlassian help.jpg

Bill Sheboy

Hi @Diane Fahr

As the JQL for your conditions and the branch are dynamic (i.e., based on some variables and data) I recommend adding writes to the audit log to confirm they contain what you expected.

For example, before the Related Issues Condition you show, perhaps write this to the log:

JQL for Related Issues Condition: the JQL you use

Doing the same before each condition / branch using such JQL. When you next test your rule, you may review the audit log to help assess what you are observing.

Next, from the section of the rule you show, there are multiple JQL branches, each of which will run in parallel and asynchronously. There is no guarantee of when these will finish, up until the last rule step, and so the branches could collide with each other and other rule steps / conditions.

Kind regards,
Bill

Diane Fahr

@Bill SheboyI have added logs and it writes what i expects and the branches are set up in such a way I do not car what order they run in .. the perplexing thing to me is

why pass in the if and fail on the branch, I am not changing the values that were passed in via the web hook .. I will post more data after I collect additional log information .

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center

jira-automation