Powering a gannt chart with JIRA

[Stephanie Willis]

We use JIRA tickets to track all of our in progress and upcoming work. This works great for the individual people working on the tickets. For communicating what is upcoming on our roadmap to people outside of the department or to the executive team, JIRA doesn't work well. So we have people duplicating their work by creating powerpoint slides or excel files that show a gannt chart of their work.

Is there a way to export tickets from JIRA that we could import into Excel that could easily power a gannt chart for us? I can figure out the formula aspect of it, but I'm not sure if it is possible to export information from JIRA that way. (We may need to add data to our tickets for this to work, I know... For instance if we put estimated times on all our tickets?)

Alternately, is there a good plug-in that can help us with this? We have the Cloud version of Atlassian and most of the plug-ins I see get very bad reviews, so I'm wary of them. 

Anyone else trying to solve a similar problem?

[Stephanie Willis]

Thanks for replying! Exporting it this way might work. My concern is the 1000 limit, but perhaps we could find a way to write our query to prevent that. 

[Deleted user]

Cool! I'm happy to hear that might work for you. Unfortunately with paging, it means you would need to make multiple (GET) requests. It's that way for fair reasons (wouldn't want to allow folks to hit your server for all records at once...).

JIRA's docs on pagination are pretty decent, and it's super nice they include an "isLast" parameter to check if the current page is the last one: https://developer.atlassian.com/cloud/jira/platform/rest/#pagination

[Deleted user]

I see a similar question was asked back in 2015. I've not played with Cloud yet, have you already looked at this suggestion (and found it unhelpful)?

https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-export-issues-to-csv-file-programmatically/qaq-p/553755

If it's possible to call (GET) the csv export URL, then you could write a script and call it on a scheduled basis with a dedicated user scoped with access to the issues it needs access to. Seems in-general the REST api returns json and not csv--so the CSV export is probably the way to go if possible (unless you want to convert that to CSV).

Note, it looks like you may need to page the results if you have more than 1000 issues to export at once:

https://confluence.atlassian.com/jirakb/export-more-than-1000-issues-to-excel-from-issue-navigator-in-jira-cloud-779160811.html

https://confluence.atlassian.com/jirakb/changing-maxresults-parameter-for-jira-cloud-rest-api-779160706.html