JQL Branch Automation not finding issues

Raphi Levine February 27, 2024

I have an issue where JQL branch automation is not finding the issue.

When I run the JQL in a filter it is returning data. 

When I validate in the automation module (after adding the JQL condition, there is a validate link which shows that it found data), however when the automation runs it is not finding any data.

Any help on this?

3 answers

2 accepted

2 votes
Answer accepted
Kalyan Sattaluri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 27, 2024

Hello @Raphi Levine 

You dont need a branch in your rule.

Just put your JQL in your "scheduled" trigger JQL section and do your actions of edit / transition right after your trigger.

Branch is needed when you are trying to do something related to issues. Such as a newly created issue etc. You dont have such set up. Please review below articles for more understanding.

https://support.atlassian.com/cloud-automation/docs/what-is-rule-branching/

https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/

 

Raphi Levine February 28, 2024

Thanks @Kalyan Sattaluri

This has helped me figure out the issue.

Even if I do branching, it should still work.

The issue was that I started by adding a JQL in the Schedule task which was limiting it to only 1 type.  DUHHHH!!!  :)

Thanks for you input!!

Like # people like this
0 votes
Answer accepted
Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 27, 2024

Hi @Raphi Levine ,

Can you share your actual requirement and screenshots of the rule ? 

Raphi Levine February 27, 2024

See below rule (note the validate issue link shows that 1 issue found).  Also see below, the exact same query (copy and paste) runs and shows an issue.

Yet, when the automation runs it does not find this issue.

Also note, that I had a different issue type and the query finds both issues, however when the automation is running, it is consistently not finding the same issue (that is shown below).

jql_Automation.png

Screenshot 2024-02-27 223246.png

Raphi Levine February 27, 2024

I should note, that I have tried testing changing the query to only find items in the specific status (no other JQL statements included) and even though the filter returns data, when the automation is run, it is not finding this task.

Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 28, 2024

Hi @Raphi Levine ,

You can just create rule without branches. When created the rule, you can enable "Run a JQL search and execute actions for each issue in the query" and input your JQL there.

image.png 

Once the JQL is added, THEN add required actions like Edit issue, Transition issue, Send email.

image.png

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 28, 2024

Hi @Raphi Levine 

When writing a rule and testing the JQL with the "validate" link, it uses the permissions of the person editing the rule.  But when the rule triggers, it uses the permissions of the rule actor.

Have you checked if the rule actor has been changed from the default of Automation for Jira?

Kind regards,
Bill

Raphi Levine February 28, 2024

HI @Bill Sheboy ,

Yes both users have permission and I tried running as me as well (I have permissions) and it still is not finding it

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events