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,556,658
Community Members
 
Community Events
184
Community Groups

My automation rule for sum the estimations of subtasks is not working

I need some support since I configured an automation rule for doing an autosum of the estimations of the subtasks in the parent task.

The event is triggered on the creation or edit of subtasks tickets, and it is supposed to be running correctly with status sucess for every edit but the sum is not executed neither reflected on the parent task>

Sucessful status with no updates on my ticket

Screenshot 2023-04-17 172338.png

My current automation rule
Screenshot 2023-04-17 172407.png

The parent task that is supposed to be updated with the sum of the subtasks estimations:
Screenshot 2023-04-17 172448.png

 

Please let me know what am I missing.

2 answers

1 accepted

1 vote
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 18, 2023

Hello @Criselda Mora 

I believe your problem is in the code that you have used:

"Story point estimate": {{issue.subtasks.Story Points.sum}}

It needs to be:

"Story point estimate": {{issue.subtasks.Story point estimate.sum}}
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 19, 2023 • edited

Great! Glad I could help.

0 votes
Callum Carlile _Automation Consultants_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 18, 2023

Hi @Criselda Mora 

Try following the example in this related post. You would need to replace any reference to 'Annual Voice Reduction' to Story Points Estimate, including where the custom field ID is referenced. You would not need to use the Advanced Field editor to achieve this.

You would then also need to clone the rule and change the trigger, as you cannot have two separate triggers within the same automation rule.

Hope this helps!

Hi Callum, I'm cleaning my other rules to check no other automation is interfering, but for the par of the advanced field I think I need it because the field is not appearing in this search even when it exists
Screenshot 2023-04-18 152402.png

Callum Carlile _Automation Consultants_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 18, 2023

Is the Story Points Estimate field an editable field on the parent task?

I think so, this is what I see
Screenshot 2023-04-18 162010.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events