automation of summing original estimate doesn't work

[Youngeun Kim]

{{triggerIssue.parent.subtasks.fields.timetracking.originalEstimateSeconds.sum.divide(60)}}

This used to work but it stopped working about 2 weeks ago

[Bill Sheboy]

Hi @Youngeun Kim -- Welcome to the Atlassian Community!

The subtasks smart value is one where the data is looked up just-in-time when used, and it does not include all of the fields, such as time tracking ones.  The same is true for the linkedIssues smart value.  This is by-design and for performance reasons.  If rules did not do that, you could imagine a situation where a single issue pulls in the data for thousands of others!

The workaround for your scenario is to explicitly lookup the subtask data using the Lookup Issues action.  For example: 

• trigger: field changed for time tracking
• condition: issue type is Subtask
• branch: to parent
  • action: lookup issues, with JQL of parent = {{issue.key}}
  • action: edit issue, setting the original estimate to
    • {{lookupIssues.timetracking.originalEstimateSeconds.sum.divide(60)}}

As you were dividing the seconds by 60 to get minutes, you may need to add the units of measure to the end: m

Kind regards,
Bill

[David Freitez]

Hi @Youngeun Kim  

Welcome to the Atlassian community.  Can you let us know the result of the Automation Audit Log?  This way we can check if there is an error. Also, it would be good if you share the rule.

Regarding the main point which is summing the Original estimate, you can check the following community question and compare with your approach:

• Original Estimate on parent issue

Regards,
David

[Youngeun Kim]

The result is success but Original Estimate did not change.

You can see Automation for Jira has set Original Estimate to 0m even when I set Original Estimate of subtask to 6h.