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.:D
The 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 100
A 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.
BR
Kai
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.