Automation rule | How to find the count of child issues of a specific type under the Epic and store it in a custom field? | Automation | Atlassian Support
I use the article linked above which worked, however, for epics with more than 100 child tasks the total displays as 100. I've double checked them all.
For any epic with <100 tasks the number is correct. For any epic with >100 tasks the number given is exactly 100.
Can anyone see why that is?
Hi and Welcome,It is not your rule – it is the platform.:DThe automation tasks have sometimes caps inside. The “related-issues” operation caps at 100 issues per Action to protect performance on shared Cloud tenants. as the result set is larger than 100, anything after the one hundredth issue is ignored, so :• For Epics with fewer than 100 children the count is correct.• For Epics with more than 100 children the count stops at 100A list of the mimits you can find Automation service limits | Cloud automation Cloud | Atlassian Support A possible workaround could be to call with the webrequest action the api.
GET /rest/api/3/search?jql=parent=EPIC-123&startAt=0&maxResults=1000&fields=key
and then use
{{webResponse.body.total}}
to get the total. BRKai
Thanks @Kai Krause do i include the webrequest in the automation query? Do you have an example of how I put that in?
You can add an send Web Request Action into your automationHere is a short help from atlassian. Automate Issue Field Updates Using Jira Cloud REST API | Jira and Jira Service Management | Atlassian SupportSetup the proper Url to your instance and the authentification. the url should be https;//<YourDomain.atlassian.net>/
/rest/api/3/search?jql=parent=EPIC-123&startAt=0&maxResults=1000&fields=key
using a smartvalue and not EPIC-123 Would be soimething like that and after this you can log or use , to get the result.
BRKai
I'll give it a go thanks!
It looks like you're new here. Sign in or register to get started.
