Trouble understanding insights data

[Sandeep Gowda]

I am not able to understand the attached data from 'Insights'.
How is the number so low?
How is it calculated?
If we carry forward previous sprint tickets to the current sprint, will the original estimates also be carried forward? Is that why it shows 2064 hours? 

Thanks, 

Sandeep

[Iryna Menzheha_SaaSJet]

Hi @Sandeep Gowda  👋
Welcome to the Community!

Let’s break this down.

What you’re seeing:

The “Sprint Commitment” insight compares:

• The total committed time in your current sprint (e.g., 2064h 38m),

• With the average time spent in past 5 sprints (17h 24m).

That huge gap likely means:

1. Too many issues were added to the sprint compared to the team's usual workload.

2. Or — as you guessed — carried-over tickets from previous sprints retained their original estimates, making the committed time much higher than actual effort needed.

So yes — when you carry tickets forward, original estimates stay unless manually adjusted. This can cause inflated numbers like 2064 hours, especially if large epics or multiple stories were pushed forward.

Also you can try Time in Status to track what’s really happening inside your sprints:

• See how long each issue actually spent in statuses like "In Progress", "Code Review", or "Blocked"

• Analyze completed vs. carried-over work

• Filter by sprint, assignee, or label

• Export real work time vs. estimated time for analysis

You can even have Sprint Report, which shows:

• Completed issues

• Incomplete issues (carried forward)

• Scope changes during the sprint

App developed by my team.

Let me know if you’d like help setting up your first report or demo!

[Danut M _StonikByte_]

Hi @Sandeep Gowda,

Welcome to the Atlassian Community!

Have a look over the Atlassian documentation available here: https://support.atlassian.com/jira-software-cloud/docs/understand-backlog-insights-in-company-managed-projects/

Basically, this chart calculates the average velocity for the past 5 sprints. In your case, I think is the average time spent by the team in every sprint: 17h 24. Then it makes a recommendation about how many hours to commit in the next sprint considering the calculated velocity. In your case is 15-20h, which apparently is far less than what you already committed in Sprint 33 (2064h)...

I don't know exactly how it calculates... maybe your team logged hours on sub-tasks?! Most likely this chart does not include the sub-tasks in the calculation, so please check.

If you don't figure this out, my advice is to also look at the Jira Velocity report, to see the numbers in every sprint. Or, to search for an app on Atlassian  Marketplace that provides similar info.

If you consider the idea of using an app, you could also look at the Team Velocity gadget offered by our Great Gadgets app, which offers more info and has support for sub-tasks and other types of estimates.

Find more about this gadget here: https://community.atlassian.com/forums/App-Central-articles/8-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063 

Danut.

[Anshul Arora]

Hi Sandeep,

You can find details on Backlog Insights here

https://support.atlassian.com/jira-software-cloud/docs/understand-backlog-insights-in-company-managed-projects/

Regards,
Anshul