nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation - Sum Subtask Estimates to Story Not Working

roger.sun

I followed several articles on how to set a JIRA automation to sum up 'Task Estimates' up to a field on the Story level called 'Groomed Estimate'. Despite the audit log saying success, the 'Groomed Estimate' value remains null. Seeking help!

Rule:
Screenshot 2023-07-12 at 9.49.04 AM.png

Audit Log:

Screenshot 2023-07-12 at 9.49.43 AM.png

Setting Subtask value of 'Task Estimate' to 4:
Screenshot 2023-07-12 at 9.50.48 AM.png

Parent issue / Story field value of 'Groomed Estimate' remains null:
Screenshot 2023-07-12 at 9.51.03 AM.png

Accepted answers

Trudy P Claspill

Hello @roger.sun

Welcome to the community.

An excellent tool to help debug Automation Rules is the Log action. You can use the Log action to print any smart value into the Audit Log of the rule execution.

Try using the Log action to print out the smart value you are trying to assign to your Groomed Estimate field and see if it actually has a value.

Also, what type of fields are Task Estimate and Groomed Estimate?

And from where specifically did you get the idea for using {{issue.subtasks....}}?

All comments

Trudy P Claspill

Hello @roger.sun

Welcome to the community.

An excellent tool to help debug Automation Rules is the Log action. You can use the Log action to print any smart value into the Audit Log of the rule execution.

Try using the Log action to print out the smart value you are trying to assign to your Groomed Estimate field and see if it actually has a value.

Also, what type of fields are Task Estimate and Groomed Estimate?

And from where specifically did you get the idea for using {{issue.subtasks....}}?

roger.sun

@Trudy P Claspill

Also, what type of fields are Task Estimate and Groomed Estimate?

They are both set as Number fields

And from where specifically did you get the idea for using {{issue.subtasks....}}?

Atlassian put out an article on how to sum up story points

Trudy P Claspill

Thank you for that additional information.

It looks like you are working with issues in a Team Managed project. Is that correct?

I have tried using the {{issue.subtasks...}} smart value in Automation rules for both a Company Managed and a Team Managed project to sum values from a Number field in subtasks to another Number field in the parent issue and it has worked.

What do you get when you print the smart value with the Log action? It is possible that there are multiple fields across the system named "Task Estimate" or "Groomed Estimate" and the Automation is working on the wrong fields. You may have to use the custom field id for one or both of the fields instead.

roger.sun

It looks like you are working with issues in a Team Managed project. Is that correct?

Yup, you are correct

It is possible that there are multiple fields across the system named "Task Estimate" or "Groomed Estimate" and the Automation is working on the wrong fields. You may have to use the custom field id for one or both of the fields instead.

Although we do have several projects, this is the first project using Task Estimate and Groomed Estimate

What do you get when you print the smart value with the Log action?

Can you share an example of the formula you're suggesting?
I tried the below. The system does recognize that the subtask Task Estimated has updated and has a parent Story. However the parent Story itself seems to not recognize the subtask ID and cannot pull the Task Estimate from it.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud