JQL Branch Automation not finding issues

[Raphi Levine]

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?

[Kalyan Sattaluri · Accepted solution]

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]

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!!

[Marc Isikoff]

I am not tracking this: you don't need a branch in your rule...

I am using branching on JQL to isolate an epic for the purpose of assigning its key as the epic of the triggering issue.

When I run that JQL in a filter I get one returned row; when I run it in the branching for JQL it gets no values returned.

And this is a basic JQL: project = abcdef and issuetype = epic and summary ~ ######

Scheduling will not work for this.

So back to basics: why is JQL getting no data in branching, but the same JQL gets data as a filter?

[Rilwan Ahmed · Accepted solution]

Hi @Raphi Levine ,

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

[Raphi Levine]

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).

[Raphi Levine]

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]

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.

 

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

[Marc Isikoff]

Are you crossing projects? I ask because you specify the project = auditing department and in Jira automations, you need to construct the automation as a global rule, not a project rule if you are crossing projects else you will not find your results.

[Bill Sheboy]

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]

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