Why AQL Branch Option does not show in JSM Project Automation?

[José Henrique Lincoln Da Fonseca Felizardo]

Guys, I have a question and I looked for an answer but I couldn't find it.

Why does the "AQL" option sometimes appear as a "Branch" option in Automation, and other times this option does not appear?

Even though it is in a JIRA Service Management project, sometimes it does not appear, but in the same project it sometimes appears.

I'm setting up Single Project automation, in a JIRA SM project.

[Joseph Chung Yin · Accepted solution]

@José Henrique Lincoln Da Fonseca Felizardo -

Welcome to the community.  Based on my understanding there is an AQL condition available however it is not available for Create a branch section yet.  Even though it is listed in Atlassian's reference page on branching - https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/

I have not personally used the AQL branching in automation rule.  I would recommend you to contact Atlassian Support (https://support.atlassian.com) for further assistance.  Once you obtained their feedbacks, please post the feedbacks back to this case again, so others (including myself) will be able to understand better.

Sorry.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[José Henrique Lincoln Da Fonseca Felizardo]

Hi @Joseph Chung Yin  

The curious thing is that sometimes it appears.
See this image I just captured. The difference is that this automation was created by Global Automation.

[Joseph Chung Yin]

@José Henrique Lincoln Da Fonseca Felizardo -

I can confirm that is correct.  This AQL branch is only available when the rule is set to GLOBAL scope.  It is odd that it is not documented anywhere in the documentation wiki pages.

You must consider the new policy on the new process where automation rule execution is counted (starting at Nov 1, 2023) - https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update.

The global scoped rule will run across all projects.

The reason why you need to consider this because "Global" scope rule execution will directly be counted against your env (Ex. Premium subscription is 1000 per each user/agent license).  So if the rule is fired unnecessary, your rules may stop to execute if the limit is reached.

Hope this helps.  If my suggestion helped you, please click on "Accept answer" when you have a chance, so others with similar asks will see this posting as an answered entry.

Best, Joseph