Creating Burn Down and Velocity charts using Insights in GitHub projects

[vikas-chinchansur]

Select Topic Area

Question

Body

Hello,

I am looking forward to create a charts using Insights for the GitHub project issues.
Below are the list of charts I need to create:

1. Burn down chart (Line Chart)
   X-axis: Sum of task estimates (Story points)
   Y-axis: Current Iteration timeline (days)

2. Velocity chart (Bar Graph)
   X-axis: Sum of task estimates (Story points)
   Y-axis: Sprints (two bars for each sprint - Commitment and Completed)

It would be great if anyone please send me the help links describing the steps to implement them.

[minware-dan]

Hi @vikas-chinchansur -

Were you able to solve for this? I have yet to see a high quality native solution -- you could export or pull this information into a BI tool for custom reporting but I suspect you will run into challenges unique to how milestones are being used. DIY will not be as straightforward as some of the other project management tools out there

Build vs. buy:: I am a co-founder at a company called minware - we offer an Agile Intelligence tool that recently integrated with Github Issues so my team is familiar with the challenges you will run into trying to build these reports. I definitely recommend checking out our free trial before you try to DIY.

[minware-dan]

Hey @vikas-chinchansur hope all is well! Curious if you were ultimately able to solve for this?

[minware-dan]

@kazza7ambientes anything specific you are looking for? We have a domain specific language called minQL that allows for complete customization. Check out the live reports + builder and self-guided demo on our homepage if you want to learn more.

[chiedo]

Hey @vikas-chinchansur!

For the burn down chart, can you elaborate more on what you're looking for?

Are you expecting to see the total number of story points for open issues in the current iteration graphed over time from the start of the current iteration until the end of the current iteration?

[chiedo]

That's beautiful! @rileybroughten has taken over in this area so looping her in.

[vikas-chinchansur]

@timbomckay Thanks for sharing this, its stunning and the details in chart are actually whats needed in our projects.

[rafaribe]

@chiedo We ended up creating a GitHub action to use the GraphQL API to gather project details and generate our own burndown chart using Chart.js (as GitHub does) and GitHub's colors:

Would really love for this feature to be in the Projects Insights view as an officially supported metric.

Is this action open-source (or is planned to be) ? Couldn't find it in the marketplace. The chart looks absolutely stunning.

[timbomckay]

Is this action open-source (or is planned to be) ? Couldn't find it in the marketplace. The chart looks absolutely stunning.

Thanks @rafaribe, I didn't do much more than use chart.js & GitHub colors haha. It's not open source right now, it was a bit of a rush job for work. I'll look into creating a repo for it and what hardcoded details can be converted to fields.

[leelas-pm]

Hi @timbomckay! Was just wondering if you would still consider creating a repo for the burndown chart above? I'm obsessed with it, it's basically perfect haha

[tohagan]

Not used it but I found this GH project to display Burn down charts

• https://github.com/thehale/github-projects-burndown-chart

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[timbomckay]

@rileybroughten is there any update on this or will it get archived into the abyss?

[devinallen-07]

Would love to see some burndown charts in gitHub projects.

[Flecart]

Updates?

[brian-becker-fsn]

@rileybroughten -- are you still over this? And if so, can you give us some type of indication if we are heading in the direction of burn down charts. And, then, from the backseat, "are we there yet?"

[minware-dan]

I bet "abyss" -- check out minware!

[msdisme]

and this is why we ended up moving to zenhub . . . .

[JerryNixon]

A burndown is table stakes to project management. What's going on?

[minware-dan]

@JerryNixon what insights do you think you are missing out on by not having this? (Disclosure: I am a vendor that can provide support).

[beingminimal]

@rileybroughten Please share an update or progress. Awaiting your response. Thanks

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[nmwael]

Bump
@rileybroughten -- are you still over this? And if so, can you give us some type of indication if we are heading in the direction of burn down charts. And, then, from the backseat, "are we there yet?"

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[andreaslech]

We had the same issues with limited Insights capabilities.
Out of this problem, I’ve built a lightweight tool that pulls data from GitHub Projects and makes it easy for agile teams to track Cycle Time, Time in State, Flow, and Bottlenecks without complex BI setups.
The goal is to help teams validate process improvements and make retros more data-driven.
Here’s an example of what it looks like:

If anyone is curious, I’ve shared more details here: https://flow2c.com.
Would this be helpful for your team? What metrics do you rely on most?