Get Burndown chart with JIRA API in 2020

[William Fargues]

Ok so I'm trying to reproduce the Burndown Chart from JIRA ordered by "Remaining Time Estimate" thank's to the JIRA API.

I found 2 solutions :

• "Unofficial" solution using this call :  
  http://constellation.soprasteria.com/jira1/rest/greenhopper/1.0/rapid/charts/scopechangeburndownchart?rapidViewId=2269&sprintId=2966
  I have all the information I want (remaining time estimate for each issue, for a given sprint and over time) but I've read that this is a bad idea to use Greenhopper because it can be deprecated at any moment (is that true ?).
• "Official" solution :
  There are 2 APIs : Jira Cloud Platform and Jira Software Cloud
  I'm using this API call : 
  http://constellation.soprasteria.com/jira1/rest/agile/1.0/sprint/2966/issue
  I get all the issues for a given sprint but they are not over time.

So I don't know what I have to do. Do I have to use the "unofficial" solution or can I get the Burndown Chart from the "official" APIs ?

Thank's !

@David Leal @Nic Brough -Adaptavist- @Timothy @Raimundas Juska @Matt Wallace 

[William Fargues · Accepted solution]

Update on what I used :

http://myjiraserver/rest/api/2/search?jql=sprint%20in%20openSprints()&maxResults=5000&expand=changelog&fields=changelog,customfield_10105

You can find all the information to plot your Burndown Chart but it will be a bit more complicated than Greenhopper.

[Sahar]

@William Fargues 

can you support pls more details?

Where you able to use greenhoprer?

I am facing exactly the same issue i need to get data from burndown chart
and found that it is not supported in rest api but only using greenhopper which is deprecated and not easy

[William Fargues]

In fact, JIRA is using Greenhopper so there's nothing wrong if you use it. 
Also, if you find Greenhopper solution hard, the JIRA API one is even harder.

In my answer, I'm not using Greenhopper API but the official JIRA API.
You can find more information if you search for JIRA API JQL (this is what I used).

Basically here, in my request, I'm saying :
Get all the open sprints with a maximum of 5000 results and add the changelog field.
This is in the changelog field that you will be able to retrieve more or less the same data than Greenhopeer API.

[Michal Gasparovic]

Well, neither the urls that you can use to get the issues that belong(ed) to the sprint is returning the issues that were part of the sprint but were removed from the sprint while the sprint was active, you won't find those issues but you can see them in the burndown chart.

This whole thing is a pure nightmare.

- <instance>/rest/agile/1.0/sprint/437/issue?startAt=0&maxResults=5000&expand=changelog&sprintId=437&jql=type!=%27Sub-task%27
- <instance>/rest/api/2/search?jql=sprint%20in%20(437)&maxResults=5000&expand=changelog

how can I get the issues that were also part of the sprint but removed from sprint at some point. do I seriously have to traverse all the issues for the whole board and do it manually ?!!

[Maurycy Widera]

Hi,

It would be really nice to get some kind of update on this topic.

The Greenhopper API is not BI friendly. We would like to build our own Power BI charts seeing trends across several boards and sprints.

Similar to this post there is a lot of complexity in transforming JSON event data into 'complete snapshots' of issue status at a given point in time. Currently we would require to build up such view 'outside of JIRA' API using some kind of a script or a really complex DAX logic.

Thanks,
Mau