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

∑original estimate ∑Time spent usage

Lets say there is an parenet JIRA issue and under it, it has 3 Sub-tasks.

each sub tasks has each own Original estimate and Time logged.

To sum them to show in parent JIRA issue ticket, is it right to use following field in parenet JIRA Issue type?

∑original estimate

∑Time spent

1 answer

1 accepted

6 votes
Answer accepted
Andreas Knecht
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 28, 2020

Hi @Taeseok Ou ,

So to solve this you can use our new aggregate math functions to sum up the original estimate on all sub-tasks. For example here's a rule that will sum up the original estimate whenever it changes on a child issue and update the parent:

sum-estimates.png

The smart-value that you need is this:

{{#=}}{{issue.subtasks.timetracking.originalEstimateSeconds.sum}}/60{{/}}

(the division by 60 is necessary, since the original estimate field requires its input in minutes)

 

To aggregate the 'time spent', you probably want a second rule that looks something like this:

  • Trigger: Work logged
  • Condition: issue type is sub-task
  • For parent related branch
    • Log work on parent issue (and copy value from trigger)

Hope that helps!

Cheers,
Andreas

Thank very much Andreas for detailed and kind solution.

By the way, 

what is then following two for which purpose?

∑original estimate

∑Time spent

Like # people like this

oh,,,, the other Reply on my other similar question says below what I asked just above thread. Thanks!

----

We have a feature request created with our development team to get it implemented:

Sum estimates from sub-tasks in user stories 

@Andreas Knecht I got this example to work, but how do I present the result in a pretty print format, e.g. "2d 4h"?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events