Forums

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

Sum original and remaining estimate on epic level

Kim Ranch Olsen
Contributor
January 24, 2024

Hi all,

I have the need for summing the original and remaining estimate on all child issues on an epic.

Via this article, I found a way to summarize estimates on all children. However, this summation is triggered by a change in value for the Time Tracking or Log Work fields and does not capture the cases where issues are added to- or removed from epics. In the latter case I have been forced to create a scheduled job as it is not possible to create a trigger in cases where a child is removed from an epic (according to this article). When using the scheduling the summation returns an error. I expect it has something to do with the way it is triggered. I hope you can help here.

I am on a company-managed cloud project and I am an admin in the project in question.

Example of the error, which occurs for all epics found by below JQL:

ETRMP-6978 (Specify a valid value for Original estimate (timetracking_originalestimate), Specify a valid value for Original estimate (timetracking))

Here is a rule where the summation works

rule works.jpg

 

Here is the rule that returns an error:

Rule error1.jpg

The schedule runs the following JQL:
issuetype = Epic AND status not in (Done, Cancelled, Open) AND "Requesting Team" = etrm. 

(The cron expression is modified a bit to make testing easier).

schedule.jpg

 

The summation of timetracking and remainingEstimate:

Summation.jpg

1 answer

1 accepted

0 votes
Answer accepted
Bill Sheboy
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.
January 24, 2024

Hi @Kim Ranch Olsen -- Welcome to the Atlassian Community!

First thing, thank you for posting the details up front for your question...that helps to narrow things down.  The only thing missing is an image of the audit log details, showing that error in the context of which rule steps happened.

Your rule is using a scheduled trigger to gather the epics to process, and then update them...However, the Lookup Issues action to gather their child issues is missing, and when you reference {{lookupIssues...}} values in the rule, that is empty / null.

Please try adding the missing action and re-test.

Kind regards,
Bill

Kim Ranch Olsen
Contributor
January 26, 2024

Hi Bill

Thank you for the fast response and your help. Adding the Lookup Issues action did the trick :)

Like Bill Sheboy likes this
Omar Basyouni
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 12, 2024

@Kim Ranch Olsen  can you share the automation rule guide because i was trying to implement it and it keeps on failing 

Kim Ranch Olsen
Contributor
September 12, 2024

Hi @Omar Basyouni ,

Sure - here it is. I added a check on Cancelled status, as I do not want cancelled issues to be included in the sum of Original Estimate.

EpicSum1.jpg

Like Omar Basyouni likes this

Suggest an answer

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

Atlassian Community Events