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,558,788
Community Members
 
Community Events
184
Community Groups

Automate custom field in parent link based on % value from child links

Hello,

I need an automation which does the following action:

  • Automate the average field "Avancementt" in parent link based on values of field "% Avancement" from child links.

What i have got so far:

automation_avancement.PNG

 

Basically, when the values for "% Avancement" of ISPF-292, ISPF-290 (Linked issues) and ISPF-291, ISPF-288 (Child issues) are changed, the calculation of the field "Avancementt" should occur on ISPF-289 (Objectif - Parent Link).

But the problem is that the average is being calculated with only the linked issues.

automation_parentLink.PNG

Can anyone help how to calculate the average for field "Avancementt" in parent link by considering all linked issues and child links?

Thanks.

1 comment

Curt Holley
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 18, 2023 • edited

Repeat the branch process, but this use either Sub-tasks or Stories (or other issues in Epic) depending on which of those two scenarios is the case.

Then you'll need to add the two together and average them. So you will likely need another field to store the child based data in, then put the 2 together.

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events