Hi community,
I'm trying to roll up subtask original estimates to the parent story automatically in a team-managed Jira project.
What I've already tried:
{ "fields": { "timeoriginalestimate": ... } }Result: field ignored — timeoriginalestimate not available in team-managed
{ "fields": { "timetracking": { "originalEstimate": "..." } } }Result: edits the subtask itself, not the parent — no "Parent of trigger work item" option in team-managed dropdown
https://mysite.atlassian.net/rest/api/3/issue/{{triggerIssue.parent.key}}Result: 404 — smart value doesn't resolve in URL field
What I need:
When a subtask's original estimate is updated → calculate sum of all sibling subtasks' original estimates → write total to parent story's original estimate field → visible in backlog without entering each story.
Questions:
triggerIssue.parent.subtasks.originalEstimateSeconds.sum work in team-managed at all?Thanks!
Welcome to the community.
Whenever you ask for help with an Automation Rule it will help us to help you if you provide:
1. what type of project is this (e.g., company-managed, team-managed, etc.),
2. images that show your complete rule.
3. images showing the details of any relevant actions/conditions/branches.
4. images showing the Audit Log details for the rule execution.
5. Explain where the issue is.
These questions are not for not willing to help, but to have community members understand on how automation works.
NOTE, you will need a branch to the parent, as you trigger the rule on the sub-taks it needs to branch out to the parent.
{{issue.timeOriginalEstimate}} is the smart value for the field Original Estimate
Also check this post a reference, https://community.atlassian.com/forums/Jira-questions/How-to-calculate-total-time-spent-on-stories-bugs-and-adding-it/qaq-p/2912419
FYI -- that linked question you provided is for Jira Data Center automation, not for Cloud (which this question appears to be).
And for Cloud, I do not believe the {{issue.subtasks}} smart value contains all of the fields due to just-in-time read access, timing problems, etc. Thus, a Lookup Work Items action must be used with JQL to gather the subtasks' data for the parent, and then sum with:
{{lookupIssues.timetracking.originalEstimateSeconds.sum|0}}
Then add the units of measure for seconds when updating the parent.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.