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; } } }

Why do a template repeat a JQL query inside a branch?

Luiz Eduardo Freitas Santos

On an template (to send an email when an issue aproaches the due date), the JQL query is repeated again inside a branch (the loop for each Assignee). It was already executed at the begining to return the desired issues...

Why?

Accepted answers

John Funk

Hi Luiz - Welcome to the Atlassian Community!

Can you share the rule that you have so far? And then what's wrong with the results?

All comments

John Funk

Hi Luiz - Welcome to the Atlassian Community!

Can you share the rule that you have so far? And then what's wrong with the results?

Luiz Eduardo Freitas Santos

The rule is from a template - When a task is close to the due date then send an remainder email (or something like that is the text on the templates available). The JSON exported to the rule is too big to post here (too noisy).

But the logic is:

When: Scheduled (every day at X o'clock)

Then: Create a variable (somevar)

And: Do a search, a JQL expression with the 'somevar'

For each: some smart value from the JQL resultset

Then: Do a search, a JQL expression with the 'somevar' (AGAIN!?)

And: Send an email with some smart value from the JQL resultset

Bill Sheboy

Hi @Luiz Eduardo Freitas Santos

Would you please post images of your complete rule and the audit log details showing the rule execution? Those may provide context for what is happening, as I suspect this is either a branching or a variable scope issue.

Kind regards,
Bill

Luiz Eduardo Freitas Santos

It is not an issue (apart from the lexical repetition), it works, it is Jira Software's own template... I just want to know why the JQL is repeated inside the loop branch.

Bill Sheboy

The reason I asked to see an image of the rule is what you describe is not possible: nested branching in automation for Jira rules.

And so I believe we are not aligned on how you are describing the rule and my understanding of it. Seeing the rule will confirm that.

Without seeing your rule...

I hypothesize you are seeing one or more JQL conditions and instead describing them as iterations/branches. A JQL condition can perform tests on issues to decide if the rule can proceed but it cannot supply issues for later processing.

If you instead you are asking about re-creating a variable inside of a branch, there are two possible scenarios for this...

There is no edit function for created variables. Instead a variable can be created before a branch (on a single issue), the variable can be recreated inside of the branch, and then the updated variable is available after the branch. This is a special case, because...
If your branch is on multiple issues, creating and using a variable inside of the branch may not work as you expect. Branches on multiple things are executed in parallel and asynchronously. And so each time a variable is created in such branches it is new, and thrown away after each item processes.

To learn more about branches, please look here: https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/

To learn more about conditions, please look here: https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud