Issues with getting 0m when summing Original Estimate for Epics

nicholas kurtz April 19, 2024

Currently I'm writing an automation which will sum all of the Original & Remaining Estimates for an Epics' children. The issue is that it is returning with 0 min. The children have been verified to have various timetracking values, but I'm having difficulty accessing them within logging.

Screenshot 2024-04-19 104744.png

 

After running this script on a child of an Epic it updates the Epics time estimates to 0m.

Screenshot 2024-04-19 104853.png

Any help would be greatly appreciated.

1 answer

0 votes
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.
April 19, 2024

Hi @nicholas kurtz -- Welcome to the Atlassian Community!

First thing, I am using Jira Cloud and not Data Center version, and so cannot verify what I am suggesting.  My ideas are based on what I know about automation rules.  With that out of the way...

There are several smart values for time tracking, some of which are human-readable and not numeric.  Please try writing these numeric ones to the audit log to confirm if they have values:

{{lookupIssues.timetracking.originalEstimateSeconds.sum}}

{{lookupIssues.timetracking.remainingEstimateSeconds.sum}}

 

Kind regards,
Bill

nicholas kurtz April 19, 2024

@Bill Sheboy 

 

Sorry to say that they are reporting 0's.

Screenshot 2024-04-19 120122.png

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.
April 19, 2024

Thanks for checking those fields.  I just reviewed the open suggestions and found the Lookup Issues action for Jira Data Center does not yet support those fields: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877

The same thing happened when Lookup Issues was added for Jira Cloud, and it was about a year later when all of the other fields were added.

 

For now with your current scenario, there is only one work-around:

  • Use the Send Web Request action, call the REST API function for an issue search
  • Then use the response the same way a lookup result would be used to sum the fields

If you want to try that approach, here is a how-to article for calling the REST API from a rule, and what I believe is the specific function you need to call:

https://community.atlassian.com/t5/Jira-Software-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

https://docs.atlassian.com/software/jira/docs/api/REST/9.13.0/#api/2/search-search

Suggest an answer

Log in or Sign up to answer