Sprint Burndown Insights not showing
Asked by Oliver Stutz:

Hi there,

I was on a Team Managed project and swopped to a company managed one.

The sprint burndown was a bit buggy before but still worked. Now I don't see it working at all.

1. I have it set to 'Story Points'

2. The issues are estimated.

3. I am a little confused between using Story Points and Estimate, but changing one seems to change other and I imagine this means they are linked? I prefer using the one that appears next to the priority ('Estimate', but in the card it shows 'Story Points' as that is the one that shows and works better there).

Please see attached graph showing 0. When going to reports burndown I do see it, also attached.

Would be nice to get the little graph working as the placement is great.

Thank you!

![Screenshot 2024-06-21 at 5.14.00?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/331127i5674444E400EC88F/image-size/large?v=v2&px=999 "Screenshot 2024-06-21 at 5.14.00?PM.png")![Screenshot 2024-06-21 at 5.13.47?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/331126iF784AFB71F5FFB47/image-size/large?v=v2&px=999 "Screenshot 2024-06-21 at 5.13.47?PM.png")![Screenshot 2024-06-21 at 5.13.14?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/331128i51930D0EE83DD2AA/image-size/large?v=v2&px=999 "Screenshot 2024-06-21 at 5.13.14?PM.png")


Answers:
author: Danut M _StonikByte_
body: Hi [@Oliver Stutz](/t5/user/viewprofilepage/user-id/5513864),

A better alternative to limited Burndown Insights chart of Jira is the **Sprint Burndown Burnup Chart** **gadget** offered by our [Great Gadgets](https://marketplace.atlassian.com/search?query=stonikbyte%20great%20gadgets%20agile) app.

This gadget works with any type of estimates: story points, time estimates or any numerical field. So you will be able to select Story Points even if you are in team managed projects.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/331233i6D99ED8C360C69FE/image-size/large?v=v2&px=999 "image.png")

The gadget can include the sub-tasks in the calculation and offers a detailed sprint report on its Data tab.

The app offers also Release Burndown Chart and Team Velocity gadgets, which works exactly the same; so a complete solution for tracking your team-managed projects by Story Points field. See more about these gadgets (and the many others offered by the same app) in these articles:

* <https://community.atlassian.com/t5/App-Central/8-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063>
* <https://community.atlassian.com/t5/App-Central/How-to-track-scaled-agile-SAFe-projects-in-Jira-with-Great/ba-p/1929694>

You could start with a **1-month free trial**. If you need any help, please feel free to contact support@stonikbyte.com.

Hope this helps.

Danut.

comments: author: Oliver Stutz
body: Hi [@Danut M _StonikByte_](/t5/user/viewprofilepage/user-id/502420) ,

Thank you for the detailed answer. I see it is free for up to 10 users so I may give this a go and see how it works.

Thank you.


author: Oliver Stutz
body: Hi [@Danut M _StonikByte_](/t5/user/viewprofilepage/user-id/502420) ,

Are you able to add this in the insights section or only on dashboards?

Thanks


author: Bill Sheboy
body: Hi [@Oliver Stutz](/t5/user/viewprofilepage/user-id/5513864)

Unfortunately, there are two story point fields in Jira after team-managed projects were implemented:

* company-managed projects use the "Story points" field
* team-managed projects use the "Story point estimate" field

In the UI for team-managed projects, they inconsistently display as both names, causing even more confusion.

As you have switched to a company-managed project, use only the "Story points" field. Please remove any uses of "Story point estimate" from the pages / views, and confirm that all of your issues have correctly set the field.

Kind regards,  
Bill

comments: author: Oliver Stutz
body: Hi Bill,  

Thanks for the response.

I confirm I have already removed the story point estimate field and am only using story point:

![Screenshot 2024-06-24 at 9.10.47?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/331321i5174A5B81752A752/image-size/large?v=v2&px=999 "Screenshot 2024-06-24 at 9.10.47?AM.png")

Even with this the burndown insight is not working. I will have to use the main report for now. This was just convenient due to location and daily scrums reviewing the board.

Any other possible solutions?

Thank you!


Tags: cloud

jira-cloud