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; } } }

Weekly Story Point Sync up to Feature

Ellie Tyler

Currently, my org has an automation that updates the story points on a feature every time story points are added to that feature's child stories/bugs/spikes.

However, this runs A LOT and we don't need updates that often. What I'd like is to create an automation every Friday that:

looks for features that are "in progress"
adds up the story points for story/bug/spikes that are either open or marked as done.

I've tried some stuff, but I can't get it to run correctly. It just wipes the story points from the feature. Screenshot 2025-03-10 at 11.23.40 AM.png

Accepted answers

Bill Sheboy

Hi @Ellie Tyler -- Welcome to the Atlassian Community!

First. your rule is trying to use the {{lookupIssues}} smart value but it has not first used the Lookup Issues action to gather the issues for the Feature as you loop through them:

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues

Next, you note using an issue type named "Feature". Is that at the same level as the built-in type named Epic?

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Ellie Tyler -- Welcome to the Atlassian Community!

First. your rule is trying to use the {{lookupIssues}} smart value but it has not first used the Lookup Issues action to gather the issues for the Feature as you loop through them:

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues

Next, you note using an issue type named "Feature". Is that at the same level as the built-in type named Epic?

Kind regards,
Bill

Ellie Tyler

Yes, a Feature = Epic at my org.

When doing a lookup feature, I'm guessing it's best to just make the lookup the same as the jql branch? Screenshot 2025-03-10 at 1.36.35 PM.png

Bill Sheboy

Thanks for confirming the issue types, and...

As the branch gets each "Feature", the Lookup Issues action would then find the child issues for it with this JQL:

parent = {{issue.key}}

Then the story points may be summed with this:

{{lookupIssues.Story points.sum}}

That will work if you have a company-managed project. If this is instead for a team-managed project, that uses the different "Story point estimate" field:

{{lookupIssues.Story point estimate.sum}}

Also, what is the purpose of the condition test in your rule? Shouldn't the parent always just be set to the sum?

Ellie Tyler

If a story has a status of "expired" or "closed", then we won't be doing the work. I want the story points field to only reflect work we will do.

Ellie Tyler

Hello, does this look correct? It has run twice and I'm not seeing the story points update Screenshot 2025-03-10 at 6.40.42 PM.png

Harry Peng

@Harry Peng mark

Welcome!

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

Quick Links

Find more posts tagged with

automation