Failed to use automation to aggregate estimation in the epic

Question

Hi,

What I am trying to do is to have a scheduled automation that update the original estimate and remaining estimate of epics by aggregate the stories below it. I am using Jira v9.12.12.

The trigger is a schedule that looks up all the epics not closed every X minutes:

When: Scheduled

Searches with:

project="xxx" and type=epic and status not in (Closed,Resolved,Abandoned,Cancelled)every 5 MinutesThen do a lookup "Epic Link" = {{issue.key}}Then do edit fieldOriginalEstimate, {{lookupIssues.Original Estimate.sum.divide(60}}mAccording to audit log, it succeeded (found the epic and found the issues in it), but the value is always 0. I double checked that all the found issues have value for original estimation.Does anybody know why?thanks

Trudy P Claspill · Answer

Are you working with Jira Cloud or Jira Data Center? There's a couple of ways to figure that out.

When you click on the Help icon near your avatar and select About Jira, what information do you get? If it shows a version number similar in format to "9.2.1" then you are probably using Jira Data Center.

If the domain of your site URL is something.atlassian.net, then you are probably on Jira Cloud.

The post you referenced is for Jira Cloud. If you are using Jira Data Center the functionality for Jira Automation may be different, and we would need to know what version of Jira Data Center you are using to find the relevant documentation.

Frank Zhang_8d07o5 · Answer

I don't understand. It seems that in many other posts, the original estimation is supported. such as this one: https://community.atlassian.com/t5/Jira-questions/Automation-Fill-the-Estimate-of-Epic-with-the-Sum-of-all-issues/qaq-p/1621946.

I did try use timeestimate, but it doesn't work for me either

Trudy P Claspill · Answer

Hello @Frank Zhang

One debugging tool that I leverage heavily in Automation Rules is the Log action. That lets you print text and smart values into the rule execution log.

For instance, after doing your Lookup Issues action you could add a Log action to print this:

Sum of original estimate: {{lookupIssues.Original Estimate.sum}}

Unfortunately, according to the following documentation, the Original Estimates field can't be accessed directly from the {{lookupIssues}} access. Expand the collapsed section under the heading Available properties

https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html#Jirasmartvaluesissues-lookupissues-properties

There have been suggestions in other posts on this topic to use the Send Web Request action to call the Jira REST API to get the data instead.

So far I have not found a validated example for how to use Automation in Jira Data Center to sum up Original Estimate.