Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira automation Sum up all estimation of linked tasks to parent

Svatopluk Blazej January 7, 2024

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.

obrazek.pngobrazek.png

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
obrazek.png
Now it passes but it adds 0m into parent story

obrazek.png

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:
obrazek.png

2 answers

0 votes
Svatopluk Blazej January 7, 2024

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.

0 votes
Nic Brough -Adaptavist-
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.
January 7, 2024

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.

Svatopluk Blazej January 7, 2024

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

obrazek.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events