JIRA Automation Rule for FixVersions unreleased

[ignacio_elorriaga]

Hi all!
I am looking for the way to created this rule but I am struggling on how to achieve it properly. 
(We have JIRA Datacenter)
I want to have a monthly rule that looks for those FixVersions unreleased and overdue and then, mark them as released for those have all of its tickets in status = Closed. 

For that what I achieved is: 
JQL = fixVersion in unreleasedVersions(ABC) and status = Closed and fixVersion in overdue()
=> created the Cron job (That's easy part)

And then what I did, it was: 

2nd.- Create a Lookup Issues with that same JQL

3rd.- Branching on JQL type with JQL = "key in {{lookupIssues}}"
4th.- Release version action using the release name as {{issue.fixVersions.name}}

But I am getting some errors. and "THROTTLED"
How can I achieve it

[Bill Sheboy · Accepted solution]

Hi @ignacio_elorriaga -- Welcome to the Atlassian Community!

Short answer: your rule is exceeding one (or more) of the automation service limits...causing it to be throttled and halted: 

https://confluence.atlassian.com/automation/automation-service-limits-993924705.html

I recommend pausing and discussing this with your Jira Site Admin to help identify which limit is being exceeded.

Without seeing your entire rule and the audit log details...

The scenario you are trying is challenging with Jira Data Center automation as it does not have the Advanced Branch feature.  And so you are trying to iterate over all of the issues rather than all of the unreleased versions.

Two possible workarounds to try would be:

1) Reduce the load on the branching

• after the Lookup Issues action, capture the issue keys found the issues in a Created Variable
• use another Lookup Issues action which matches no issues; this will free the memory used for the first lookup before branching, reducing the chance of throttling
• change the JQL branch to use the variable as the source for the keys
  • inside of the branch, use smart value list filtering to identify the correct unreleased version in the branched-to issue
  • use one final Lookup Issues action for that unreleased version to find all of its issues which are not Closed
  • with an advanced compare condition, confirm no issues were found in the lookup
  • now release the version

2) Use chained, recursive rule execution as a workaround for branching; please talk to your Jira Site Admin before trying this approach.

• from your current scheduled trigger rule...
  • use a Lookup Issues action and identify the distinct, unreleased versions
  • pass that distinct list of versions to another rule, calling it with the Send Web Request action
• the second rule has an Incoming Webhook trigger, receiving the list of unreleased versions in the data
  • grab the first version from the list...
    • use Lookup Issues to check the issues
    • ...same logic as needed to decide when to release the version
  • removing the first version from the list, when there are more to process, use Send Web Request to pass the remaining ones, recursively calling this same rule

Also, I am curious: do you have a marketplace addon for JQL or is the overdue() function a built-in one for Data Center?  I do not see that in the JQL function documentation.

Kind regards,
Bill

[ignacio_elorriaga]

OMG! thanks for pointing it out. I have never though it could be so complex

I will try the 1st option