Sum up story points to an epic using next gen Jira Scrum project

[steve.hough]

Hi,

I'm trying to create an automation to sum up the story points within an epic and add that value to an epic story point field.  

I've seen online videos but they don't seem to work for next gen scrum projects.

Any help is much appreciated.

[Bill Sheboy]

Hi @steve.hough 

What have you tried thus far?  If you have an automation rule you are trying, would you please post an image of it?

For this use case, the two key differences between company-managed and team-managed (formerly called nextgen) projects are:

• Company-managed link epic to children with "Epic Link" and Team-managed use "Parent"
• Company-managed use the "Story points" field and Team-managed use "Story point estimate"

By accounting for those changes the prior example rules may work for you.

Kind regards,
Bill

[Linh Pham_Adaptavist]

Hi @steve.hough 

I wanted to share a similar post that we followed to create the same automation rule: Sum up Story points to epic

We did modify the rules for Team-managed Project (Next-Gen project) which has some differences as Bill mentioned above. 

1. We replaced the "Epic Link" with "Parent"  in the issue search query

2. And substitute "Story Points" with the "Story point estimate" field, which my teammate figured out as below: 

This is the final set-up:

And it should work! Let me know if you need help with anything :) 

Out of interest, may I ask what's your intention behind story points sum up on Epic?

We are the maker of an app called Hierarchy for Jira which automatically roll up estimates to parent issues for you (among other cool features like custom hierarchy, tree view...). We're always eager to learn more about Jira user needs and how we can help as a Marketplace Vendor. 

Cheers,

Linh from Adaptavist

[David Sengmany]

Thank you for this response!! For the above to work I had to modify that last advanced edit issues field. For some reason it wasn't registering the Story point estimate so I went to the epic exported the XML and used the custom field id there instead and it worked!

So instead of "Story point estimate" : {{lookupIsuses.Story point estimate.sum}} it became "Custom Field ID" : {{lookupIssues.Custom Field ID.sum}}

Custom field ID was taken from the XML export for story point estimate