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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Story Point Totals with Long Decimals

Our backlog and sprint story point totals are showing very long decimals, despite not containing any issues that have that many decimals on their story point ratings.

For instance, despite having 4.15 points in progress in my current sprint, the in progress point total shows 4.149999999999995. This is shown in the photo below.

This only appears when filtered to myself, when I remove all filters the team total does not have this many decimals. Additionally, this issue appears on different members of the team in different sprints and I have not been able to isolate the matter to a particular ticket.

What is causing this? How can I get this issue resolved?


ConnorScreenshot 2020-12-16 154240.jpg

1 answer

0 votes

Hello Connor,

Welcome to Atlassian Community!

Testing on my local site using the same story point values from the screenshot you shared, I was able to replicate the same issue, but only on a next-gen project.

This issue was reported as a bug a while ago. For more details, please check the link below:

Please, click on "This affects my team" and also watch to receive updates.


Hi Angelica,


Thank you for the reply. I followed the link and noted the impact and am watching the issue. I know there aren't any reported yet - but do you have any idea of potential workarounds? Perhaps only using tenths or some other numerical solution?



Hi Connor,

I tested on my local site and the only workaround would be to use a Classic project instead of a Next-gen. 

Also, it will depend on each value, and only testing one by one I was able to find the value that was causing the issue.

Screen Recording 2020-12-23 at 10.16.27 AM.gif

Got it, thank you Angelica. I appreciate your help.

Like Angélica Luz likes this

Suggest an answer

Log in or Sign up to answer
Site Admin

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