I have JIRA with the Agile plugin set up in our organization. The web interface shows burndown charts perfectly fine.
I’m building a WPF application that needs to show burndown charts from our JIRA data. Right now I can only make it work by manually setting the sprint ID and date ranges in my code. This makes it pretty static and not very useful.
My main question is how can I use the REST API to find out which sprint is currently active and get its start and end dates? Without being able to get this basic sprint info dynamically, creating any kind of useful burndown visualization seems really hard.
Has anyone figured out a good approach for this? I’ve been looking through the API docs but haven’t found the right endpoints yet.
That approach works, but I hit authentication problems when I tried it. Make sure you’re using proper OAuth or basic auth headers. The burndown endpoint is finicky - it’ll return empty data if the sprint isn’t started right or has no story points assigned. I had to fallback to calculating burndown manually through the issues endpoint when the chart API crapped out. Add error handling for sprints in weird states. Sometimes they’re closed but still show as active because of timing issues. Also, finding the board ID is a pain - you’ll probably need to hit the boards endpoint first to get the right one for your project.
The Agile API docs are confusing on this. I spent weeks fighting a similar integration and found out the burndown charts endpoint needs specific permissions that aren’t obvious. Your JIRA admin has to give the user account access to time tracking and estimation data - basic issue access won’t cut it. What saved me was building a fallback. When the burndown API craps out or gives incomplete data, I just query issues directly with /rest/api/2/search using JQL to filter by sprint. Then calculate remaining work by adding up story points or time estimates from what comes back. It’s extra work but you’ll get reliable data even when sprints are misconfigured. Watch out for timezone issues - the API spits out UTC timestamps but your burndown calculations need your org’s working timezone to match what users see in the web interface.
try /rest/agile/1.0/board/{boardId}/sprint where state=active. it’ll give u the current sprint details like start and end dates. then use /rest/agile/1.0/rapid/charts/burndownchart with the sprint ID! worked great for my dashboard project.