Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Weekly Story Point Sync up to Feature

Ellie Tyler
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 10, 2025

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

3 answers

1 accepted

1 vote
Answer accepted
Bill Sheboy
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.
March 10, 2025

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
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 10, 2025

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
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.
March 10, 2025 edited

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
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 10, 2025

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.


Bill Sheboy
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.
March 10, 2025 edited

Then I would add those status exceptions to the lookup JQL:

AND status NOT IN ("Expired", "Closed")

 

Bill Sheboy
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.
March 11, 2025

Please try to stay in one thread when responding.  That will help others reading this question in the future know if there are multiple possible solutions.  Thanks!

 

Your rule has a condition such that it only updates the Epic when its Story Points are greater than or equal to 0...but they could be null also.  That may be preventing the rule from making any updates.

Please post an image showing the audit log details for the rule execution, and expand all the sections at the right side > arrows so we can compare which steps ran relative to what you expected.

Ellie Tyler
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 11, 2025

Apologies! When you swap to a laptop it gets hard to find the thread. 

I ended up removing the rule for story points and the entire automation is working as expected. Thank you so much!

Like • Bill Sheboy likes this
0 votes
Harry Peng
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 14, 2025

@Harry Peng mark

0 votes
Ellie Tyler
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 10, 2025

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

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Upcoming Atlassian Automation Events