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
Here is the rule that returns an error:
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).
The summation of timetracking and remainingEstimate:
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
Hi Bill
Thank you for the fast response and your help. Adding the Lookup Issues action did the trick :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Kim Ranch Olsen can you share the automation rule guide because i was trying to implement it and it keeps on failing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.