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

Can we sum up "number" fields of all child issues and update parent's ?? (Not task/subtask)

testJira seb

Hi,

I am on DC (not cloud) and unable to find out automation rule about sum in the case

Can we sum up "number" fields of all child issues and update parent's ?? (Not task and subtask, but with ParentLink and childLink)

Remember
- child A have number field = 12
- child B have number field = 10
- Parent issue (with parentlink, not task/subtask) = 22 (first time it is correct)
- This is fine so far but
- A : 12 -> 15 (updated)
- Parent Issue = 37 (not 25 like it should)

the problem is solved if we use tasks and subtasks = a solution exists

BUT

tasks and subtasks being limited to a single level (you cannot create several nested subtasks). As a result, it is possible, for a tree structure of this type, to use the principle of Parentlink/Childlink ; and therefore no more limit to a single sub-level but as many as desired

I've seen all of these answers (about "sum" pbl), which work great for task and subtask cases.
On the other hand, it is impossible to run a procedure correctly with the ParentLink / childlink. For these cases, we fall into the same process.
Do you have a solution for this type of case?

Thanks all.

Accepted answers

All comments

Stefan Salzl

Hi @testJira seb and welcome to the community,

did a quick research and found a feature request for that. You can upvote for it here:

https://jira.atlassian.com/browse/JIRAAUTOSERVER-135

As I got your requirement and the above mentioned feature request right it‘s not possible yet.

Best
Stefan

Bill Sheboy

Hi @testJira seb -- Welcome to the Atlassian Community!

Just to confirm, are you noting that you have an automation rule and it works once and then produces incorrect results on later executions?

If so, please post an image of your complete rule, including the details of the field action, and the audit log details showing both a first and later execution run. That information may provide context for the community to offer suggestions. Thanks!

Kind regards,
Bill

testJira seb

Hi Stefan, yes https://jira.atlassian.com/browse/JIRAAUTOSERVER-135 is the same way.

we can go to parent with

issue in parentIssuesOf("{{issue.key}}")

but how to get informations about all childs ?

testJira seb

Hi Bill,

automation rule works but results are incorrect.

here is example = we don't use "task/subtask" but "parent link". so we use "issue IN parentIssuesOf( {{issue.key}} )" to get parent ... But after that, how to get info about childs ?