Jira automation Sum up all estimation of linked tasks to parent

Question

Hello,

i do have parent story: And i do want to be able to sum up all time estimations from linked issues (is subtask of) to the parrent. The trigger is set up as an update for the "is subtask of" issues.

I have red about the issue.subtasks approach but it seems that it just works for subtasks. How can i trigger "is subtask of" link?

By time tracking i mean this table

Now it passes but it adds 0m into parent story

Thanks
NOTE: {{issue.subtasks.Original Estimate.sum}} has the same behaviour, it adds 0m

{{issue.issuelinks.isparettaskof.Original Estimate.sum}} , SUM: {{#=}}{{issue.issuelinks.outwardIssue.originalestimate.sum}}/1{{/}} the same

LOG:

Svatopluk Blazej · Answer

Hello, thanks, i used audit logs, to find the correct selector for fields in this tasks,

This is the final working scheme with "{{#=}}{{issue.issuelinks.outwardIssue.fields.timeestimate.sum}} / 3600{{/}}" Edit issue input

And please note that we are not using jira for logging, thats why remaining + estimated field needs to be the same

Svatopluk Blazej · Answer

So the problem was, as i suspected by selector: this is the correct selector for timetracking fields {{#=}}{{issue.issuelinks.outwardIssue.fields.timeestimate.sum}} / 3600{{/}}
Note: change the M/H/D transition (divide) according to your config.

Nic Brough -Adaptavist- · Answer

Welcome to the Atlassian Community!

There are two problems here.

First, you should get rid of the link type of "is a subtask of".  Because the issues are not sub-tasks of the linked issues.  It's misleading for your people, as its misrepresenting what the link is.  And, of course, Jira will not be treating the linked issue as a sub-task.

If you were to use the sub-task functionality, instead of a relational link, then you would not need your automation at all - issues automatically roll up the time estimate fields on to the parent issue.

Second, if you still want to use this broken model, your automation needs to be changed - "add value to audit log" is completely the wrong option.  You need to be adding the estimate to the original estimate on the linked issue, not writing to the audit log.