Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,749
Community Members
 
Community Events
176
Community Groups

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

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.

2 answers

1 vote

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

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 ?

with task/subtask, we use "subtasks" keyword (for example, to "sum" infos)

keyword with parent and childs ?

try "childIssues" but No.

other one ? ;-)

If "parent link" is the field linking your issues, try using a Lookup Issues action to gather the sibling issues of the trigger issue with this JQL:

"Parent Link" = {{triggerIssue.Parent link"}}

You may then sum your field using the lookup results, for example:

{{lookupIssues.myCustomFieldName.sum}}

Stefan Salzl Community Leader Apr 11, 2022

@Bill Sheboy lookupIssues is only available on cloud. It´s DC in this case =S

Thanks, Stefan; I missed that!

Unfortunately Lookup Issues and nested branches are not supported yet, so the work-arounds are limited: entity properties and a scheduled rule with bulk-processing that includes a branch to the parent.

0 votes
Stefan Salzl Community Leader Apr 07, 2022

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

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 ?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events