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.
After running this script on a child of an Epic it updates the Epics time estimates to 0m.
Any help would be greatly appreciated.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
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://docs.atlassian.com/software/jira/docs/api/REST/9.13.0/#api/2/search-search
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.