Workaround for limitations around extraction all records from JIRA

[Patrick Dooley]

Hello - as other Users have, we are running into the row limitations enforced by JIRA when attempting to extract our Production Incident (PIM), Risks/Issues, and Change Requests (HCR) records.  I've not come across any 'super-JQL' queries to extract all of the different kinds of records we accumulate and my company is not interested in any tools/add-ins.

I'm interested in a work-around at this point, even if records must be extracted in stages in order to pull them all out.  For example, I will be experimenting with pulling out all of our PIMs by Year, and hope that no single year surpasses the max # of records I'm permitted to extract to Excel (which I believe is 10,000).

I would like to hear of solutions others have utilized in order to extract their records so that they can be analyzed and reported on at will.

Thank you!

[Janis Plume (eazyBI)]

Hi,

eazyBI add-on for Jira could help to create your custom reports from Jira.

Please, check our demo account here:

https://eazybi.com/accounts/1000/dashboards/4553-jira-issues-dashboard

You can have more information about the add-on in the documentation site:

https://docs.eazybi.com/eazybijira

You are welcome to try out the trial version from the Atlassian Marketplace and contact support should you need any clarifications for the report.

Kindly, 

Janis, eazyBI support

[Alexey Matveev]

Hello,

If you are on Jira server/data center, then you can bypass these limitation:

https://confluence.atlassian.com/jirakb/exporting-a-filter-result-containing-more-than-1000-issues-191500982.html

[Nic Brough -Adaptavist-]

Be aware that going a lot over 1,000 will kill your Jira - performance will degrade and it will eventually crash.

The solution most people use is reporting tools inside or alongside Jira - apps to do their reports directly, or apps like EasyBI or Dataplane which understand the data far better than an extract will.

[Patrick Dooley]

First - thank you for your responses, they are appreciated!  However, I do need to solve this data extraction request to address the needs of my Project team.  We need this data pulled out so it can be properly reported on and analyzed and we want control of the data we're entering into JIRA.  Why are they making this so difficult to extract our own data?  If we have to solve the problem by looking at other software to manage our Production Incidents/Change Requests/etc. we will, but such a transition will be painful and one we'd rather not have to engage in.  We need this data and we need assistance in designing a reasonable extraction process to get it.  Please help us in solving this issue!