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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to summarize story points over several Fix Versions?

I am wondering how I get the sum of story points over several versions.

I thought to use jira automation for that and filter for all stories in the specific versions. But how can I add the story points of story one with the story points of story two and so on?

I still try to figure out the specific samrt.value for that.

At the end I could imagine to receive an automated email every week with all open story points two one and more versions.

Does anybody have an idee how to start?

What I have so far is a trigger for each week and a filter with a loop. But I can just create an email for each story and not for the sum of all storys.



2 answers

2 accepted

0 votes
Answer accepted

Hi @Martin Hechinger ,

I know you are on server and unfortunately there is no "LookupIssue" action on Jira Server Automation but I´ll give the example on how it would work in cloud and which smart values would generate to sum of the story points. Maybe you can figure out how to fetch all the Stories of several versions.

If issues have been collected the correct smart value to summarize StoryPoints is Story Points.sum (--> see screenshot)


Hope I could at least give a little hint regarding the smart value.


Hi @Stefan Salzl 

thanks for that. yes this currently does not work, since I do not have the Lookupissue.

What I can do so far is to have a Scheduled trigger like once a day with the issues as filter included, like your lookup. Furthermore I can send an email via send email and the smart value {{issues.Story Points.sum}}.

This works fine for just one summary. But if I would like to see the sum of all issues and all open issues, I have to send two emails, which I do not like.

I am looking now for something like this to have the results in just one email:

total Story Points: {{issues.Story Points.sum}}

{{#if(equals(issues.status, "open"))}}
{{issues.Story Points.sum}} are still open

But this loop does not work, the if statement is just executed once for the first issue and takes all issues for the story points again.

Cheers Martin

Stefan Salzl Community Leader Feb 22, 2022

Hi @Martin Hechinger ,

How many and which results would you like to have in the email? The more clear this is specified the more focused the solution could be found.

Could you also provide a screenshot of your current rule (you just described)? that might also give a deeper insight and help to find a solution.


sure, right now it looks like this


With that approach, I would receive one email with all informations. Each version and the total of the versions.

Cheers Martin

Stefan Salzl Community Leader Feb 22, 2022

I´m still a bit confused by the requirements. The initial question was how to get the sum of story points of all stories to specific versions. Guess this is done with your first email. I still have some difficulties to understand what the purpose of the if and the 2nd email are.

(As I saw your German UI settings: I am Austrian and you could also describe in German to me. Maybe that makes things easier :D )



sorry for the confusion, I have changed the picture above. its a bit simplified now.

You are right, related to the title I have already all Story point over all versions. But on the way doing so I noticed to need also the sum of just one version. (or other sub-filter issues).

Cheers Martin

Stefan Salzl Community Leader Feb 22, 2022

Unfortunately I can´t think of a solution for this (at least not server without saving results to variables) as this would need filtering on different levels.

As Release/Version is not an issue itself you could not filter for released/unreleased versions and then loop over each to collect the story points (which would be necessary to gather the sum of story points of each version).

From my point of view you could rather filter

  • issues for specific version
  • issues of versions in specific state or specific property


I´m sorry but I can´t provide solution for that specific combination :(

Trotzdem danke Stefan :-)

so it still looks like, I will need one email for each result.

Since I have the result for all Versions, the title is somehow solved. :-)

Beste Grüße


Like Stefan Salzl likes this
0 votes
Answer accepted
Bloompeak Support Marketplace Partner Feb 18, 2022

Hi @Martin Hechinger

As an alternative, you can try Reports - Charts and Graphs for Jira app developed by our team.

  • You can create custom, flexible and colorful bar charts and table views for any data you want/need.
  • You can set X axis to be any parameter like Created(month), Assignee, Sprint, Fix Versions etc.
  • You can set Y axis to be any parameter like number of issues, sum of remaining estimates, average of story points etc.
  • You can group your data on any field(Sprint, Status, Assignee, Component, Project etc.) you want.
  • You can choose various date ranges like All Time, Last Year, Last 3 Months, Last 6 Months etc.
  • You can order the results by drag and drop.

Here is a sample report that shows sum of story points on each fix version. Hope it helps.

Sum of story points on each fix version.png

yes this would help. Unfortunately I do not have the plugin. So it seems like I have to do it by hand. :-(

Very thanks for showing me the motivated solution.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events