Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to sum up Original Estimates from Tasks to Epic

Søren Rangstrup August 29, 2024

I want to establish an overview of the summarized Original estimates and I succeeded in summarizing Original Estimates from sub-tasks to their parent (task level) by using the following rule:

{{issue.subtasks.Original Estimate.sum.divide(3600)}}h

See below trigger used.

Udklip.PNG

Additionally, I would like to summarize Original Estimates from tasks to their parent (Epic level) and the logic rule for this is:

 

 

{{issue.tasks.Original Estimate.sum.divide(3600)}}h

However this does not work.

How do I summarize Original Estimates from tasks to their parent (Epic level)?

3 answers

1 vote
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 29, 2024

Hi @Søren Rangstrup 

Welcome

I have this in place on my instance it it works on my end.

  • Trigger: Field value changed
    • Fields to monitor = Time tracking
  • Condition: Issue fields condition
    • Field = Issue Type
    • Condition = equals
    • Value = Task
  • Branch: Related issues
    • Type = Parent
      • Branch-Action: Edit Issue
        • Field = Original Estimate
          • Value = {{#=}}{{issue.tasks.original estimate.sum}} / 3600{{/}}

I've used "/3600" as my default time unit is hours, if your default unit is minutes, you would use "/60" instead

The Original Estimate in a smart value is shown in seconds, so you need to divide it into your default unit.

Søren Rangstrup August 29, 2024

Hi Marc

Thank you very much for your quick reply.

I have implemented your suggestion above. However, it doesn't seem to work on my end. The below shows how it looks.

Udklip.PNG

Udklip.PNG

I would like to have the Original Estimate summarized in the red circle below. 

Udklip.PNG

I would be happy if you could help me further on this.

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 29, 2024

Hi @Søren Rangstrup 

What does the audit log of the rule provide as feedback?

Søren Rangstrup August 29, 2024

Hi Marc,

Please see below.

Udklip.PNG

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 29, 2024

What is the message, you get when an error is occured?

Søren Rangstrup August 29, 2024

Please see below. I would appreciate your feedback to help me solving this.

Udklip.PNG

 

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 2, 2024

Hi @Søren Rangstrup 

This will occur when you have the incorrect smart value for the field, as it becomes an empty/null value in the expression. 

So if the field has no value, this can occur.

You could set your calculation like this:

{{#=}}{{issue.tasks.original estimate.sum|1}} / 3600{{/}}

The the field always has 1 as default in the calculation, if the field is empty in an issue. When performing the automation.

Søren Rangstrup September 6, 2024

Thanks for your feedback. However, it still doesn't work.

Udklip.PNG I got the following error:

Udklip.PNG

I hope this can help you to see what is wrong.

Søren Rangstrup September 13, 2024

Hi March

Have you had the opportunity to look into my question above?

/Søren

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 13, 2024

Hi @Søren Rangstrup 

Could you try to use: {{#=}}{{issue.tasks.originalEstimateSeconds.sum|1}} / 3600{{/}}

It might be that the divider option is not correct (3600), but this can be adjusted off course.

Søren Rangstrup September 17, 2024

I have typed in the suggested value, but it doesn't summarize. I have the following error code:

Udklip.PNG

 

If I change "3600" to "60" it summarizes any value to 0m. So It might be something with the "3600" that should be adjusted.

Could you help me further on this?

0 votes
Helen McSparron
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 16, 2024

I would like help with the above issue as well. I get so far, but my error is different to the user above. This is my query (following your example) 

Capture.GIFCapture2.GIF

This is the error message that I get in the log. I am sure the Time tracking is correct, Original Estimate is on all issue type. Wondering - is the configuration case-sensitive?Capture3.GIF

0 votes
Mehmet A _Bloompeak_
Atlassian Partner
August 29, 2024

Hi @Søren Rangstrup

Welcome to the Atlassian Community!

If you prefer using a marketplace app, you can try Sum Up Reports for Jira app developed by our team. This app provides various table reports based on the fields you choose.

App Features:

  • You can list the issue fields you want and sum up the values at the bottom.
  • You can group your data on any field (sprint, status, assignee, component, project etc.) and sum up the field values (story points, time estimate etc.) or take averages.
  • You can add this app as a gadget to your Jira dashboards.

Here is our live demo dashboard where you can see and modify any sample report and play with it.

For further details, you can have a look at Sum Up and Average Reports in Jira Dashboards article.

If you have any questions, feel free to schedule a demo with us.

 Hope it helps.

Suggest an answer

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

Atlassian Community Events