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

JIRA Automation: Get the count of selected issues

Johannes Fuenger

Hi out there,

I am not able to figure out how to set up an automation rule with the following functionality

- On a regular basis a field X of all issues of a dedicated issue type A shall be updated.
- the field X shall contain the number of issues of an issue type B where a field Y of B ,matches a field Z of A

May you help to give me at hint? I am still quite new to JIRA and struggeling around to get the funcionality implemented. Any help is highly appreciated.

Regards

Johannes

Accepted answers

Bill Sheboy

Hi @Johannes Fuenger

First thing, I recommend pausing to review some of the automation documentation. That will help you when creating a rule. To get you started on creating your rule, please refer to these documentation and example sources:

Next, I recommend clarifying your scenario by noting an example issue and writing the JQL needed to find the related issues (between types A and .

Then pause and explain that scenario to another team member. That will clarify your understanding of the problem and help to refine the needed rule steps.

Then when you write your rule, it will likely use as Scheduled Trigger with your JQL to find the first set of issues, and the Lookup Issues action to find the others. The count of issues might be {{lookupIssues.size|0}} based on that lookup result.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Johannes Fuenger

Next, I recommend clarifying your scenario by noting an example issue and writing the JQL needed to find the related issues (between types A and .

Then pause and explain that scenario to another team member. That will clarify your understanding of the problem and help to refine the needed rule steps.

Kind regards,
Bill

Johannes Fuenger

Hi Bill,
thanks for your hints and recommendation.

I used already {{Lookupissues}} and it worked. But in some cases I have >20.000 (twenty thousand) of related issues. In these cases I do not get the right count, because is reaches the limits set by the dba.

regards

Johannes

Johannes Fuenger

Bill,
the relevant Issues are linked as well, so I may use {{issuelinks.size}}. Is it possoble to get the number of links of a specific link type.
regards
Johannes

Bill Sheboy

Thanks for that additional information, Johannes.

With that many issues, you will not be able to easily get the counts. Jira triggers, branches, and lookup issues are limited in the number that can be returned / processed: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

Instead the rule could use the Send Web Request action to call the REST API issue search with JQL. Even though all issues would not be returned, the matching count of issues would be included. Please look here if you want to try that: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

Regarding issue links, you are correct that the issue links can be counted with that smart value. As linked issues are dynamically loaded in automation rules, I do not now what happens for {{issue.issuelinks.size}} if there are over the service limit counts.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

automation