Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Sprint Insights burndown still shows “We couldn’t load these details” after trying all known fixes

Sprint Insights burndown still shows “We couldn’t load these details” after trying all known fixes

Wilfred Kan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 5, 2026

Hi everyone,

I’m experiencing the following error in the Sprint Insights panel on my Jira board:

Sprint burndown We couldn’t load these details. Try refreshing and if that doesn’t fix it, contact support.

Other sections in Insights (Sprint progress, Epic progress, Work items for attention) load normally. Only the Sprint burndown section fails.

Sprint: 2026 CC Sprint 15

SCR-20260805-pqtc.pngWhat I’ve already tried:

  • Hard refresh / different browsers / incognito
  • Checked and updated originBoardId via the REST API
  • Confirmed the board is located under a Project (not a user profile)
  • Verified the board filter uses the project key (not project ID)
  • Confirmed I have the View aggregated data permission
  • Checked Estimation statistic is set correctly and issues have estimates
  • Tried the classic Reports → Burndown Chart (please mention if this one works or not)

None of the above resolved the Insights burndown error.

Environment:

  • Jira Cloud
  • Project type: Company-managed

Has anyone faced this recently and found a working solution beyond the usual originBoardId / permission / filter fixes? 

Thanks!

1 answer

0 votes
Walter Buggenhout
Community Champion
August 5, 2026

Hi @Wilfred Kan,

This looks like a (hopefully temporary) technical issue with the report. Here in Community most of us are users like yourself who don't have access to your site (or in this case the backend).

I quickly checked https://status.atlassian.com/  to validate if there are any current known issues, but that does not seem to be the case at this point. If the issue does not resolve itself soon, ask your Jira Admin to reach out to support.atlassian.com/contact#/ to investigate further.

Hope this helps! 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events