nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Wrong Story Point calculation

Andjela Milicevic

I saw that jira calculates story points as in progress even though they are in to do status

I find tickets that are calculated as in progress and their sttaus is to do, wghen I move them to done it works ok (in progress decreases), but t's wrong; they are to do not in progress.

Pictures to represent that

Accepted answers

Marc -Devoteam-

Hi @Andjela Milicevic

Welcome to the community.

The calculation is based on the column where the workflow status is placed on the sprint board.

If the To Do status is not in the first column the calculation see this as the issue in progress.

See this example where I switched the to do and in progress state on the board and how this impacts the calculation on the backlog

Screenshot 2025-09-05 at 15.52.56.png

Screenshot 2025-09-05 at 15.53.12.png

All comments

Marc -Devoteam-

Hi @Andjela Milicevic

Welcome to the community.

The calculation is based on the column where the workflow status is placed on the sprint board.

If the To Do status is not in the first column the calculation see this as the issue in progress.

See this example where I switched the to do and in progress state on the board and how this impacts the calculation on the backlog

Screenshot 2025-09-05 at 15.52.56.png

Screenshot 2025-09-05 at 15.53.12.png

Andjela Milicevic

Hey Marc,

Thanks for the fastest reply ever! This was helpful.

You are right, I didn't know that I cant have 2 columns that are in to-do status, I thought that statuses in columns define their statuses

So in my case, I assume that its the best practice to have just one to-do column and all three statuses in that column

Marc -Devoteam-

Hi @Andjela Milicevic

Please accept my answer as a solution, if my answer helped to solve or provide a workaround to your request.

This will help other community member trying to solve the same or provide them with a work around

P.S. If the answer is very valuable to you, please share some kudos.

Javier López_zse38e

Marc's answer covers the root cause well — the column placement defining workflow status is the key thing most people miss when setting up their first sprint board.

One thing worth adding for anyone dealing with story point calculation discrepancies: it helps to manually verify your point totals outside of Jira when something looks off. Jira's calculation logic can be counterintuitive when tickets span multiple statuses or columns, and having an independent calculation to compare against makes it easier to confirm whether the issue is a board configuration problem or a genuine data discrepancy.

For quick arithmetic checks on story point totals, velocity calculations, or percentage completion figures https://aliciacalculadoras.es/ shows the full step by step working for every calculation — useful when you need to present sprint metrics to stakeholders and want to verify the numbers independently before the meeting.

faheem asad

A good reminder that marking helpful answers as solutions makes the community much easier to navigate. It also helps future members quickly find proven fixes and workarounds.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud