Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Need help to fix automation rule - "Story Point estimate" field

nafis I'm New Here Jun 06, 2021

Hi All,


Our teams collectively estimate on sub-tasks attached to stories (both back-end and front end tasks) and we use this to sum up the full user story value. Yes, I know that this isn't ideal SCRUM, but there's currently good flow and accuracy with this method.


I want to automate the summing of the "Story Point estimate" values of subtasks to the "Story Point estimate" value of the user story.


I found this super useful video, but it is for "Story Points" and not the "Story Point estimate" field. Unfortunately, the isn't available out of the box here, so I must use advanced options to specify rule 


How do I do this?


*This is the line of code in the video:

{{issue.subtasks.Story Points.sum}}


*This is what I tried in the "More Options" box which did not work

{{issue.subtasks.Story Point estimate.sum}}


1 answer

0 votes

It's not "not ideal scrum", it's not doing scrum at all - sub-tasks are irrelevant when it comes to doing scrum estimates.  If you're going to do that, then you need to think through a scheme for accumulating estimates on sub-tasks up to the parent and matching them to the story estimates. 

Jira has no support for such schemes and if you implement one of the more simple schemes (as you have described) it's going to break all your sprint reporting, velocity and so-on because it's not scrum and it's wrong.

So, two things.  To implement this scheme, you need to take a slightly different approach to adding up story points

1.  Do not add up sub-task story points to the story points on the stories.  Add them up into a new custom field called something clear like "accumulated story points".  Use that as the board estimation statistic instead of the story points.

2.   {{issue.subtasks.Story Point estimate.sum}} is wrong - the field id is Story Points estimate

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

275 views 8 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you