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

Dashboard for Story points per status in a sprint

I am trying to create a report or dashboard to track the number of story points that are in each status within a sprint. I know that there is a plugin but this comes as an extra cost. I'm looking for a simple free solution. 

1 comment

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.
Jan 27, 2021

Hello @Tzaneen McGregor ,

Only two dimensional gadget will provide Status vs Other.

but Two dimensional report can't enable you to choose a story point field. 


Work around :

1. Create a new field SP (Number field)

2. Create a automation to copy value from Story points field to SP (Number field), whenever there is a change happened to Story points field.

3, Now in Two dimensional , you can choose SP VS Status.


You can add columns in JQL as required and export the data into excel. and try  pivot functionality. it will helps a bit,



I followed these steps but I still cannot access that SP field in my two dimensional gadget, does this workaround still apply in the current version of Jira Cloud?


Log in or Sign up to comment