My "go-to" answer to most JIRA reporting or data question will likely have 3 parts:
- Start with a filter. I've set up an example against jira.atlassian.com and pulled all the tickets out for five projects over the last 5 years. The JQL looks like this: project in (CLOUD, AUTO, CONFCLOUD, JRACLOUD, JSWCLOUD) AND createdDate >= "2019/01/01"
- With 25,000 Issues to process, I use the REST API and pagination to gather the details. The API call looks like this: jira.atlassian.com/rest/api/2/search/?jql=filter=XXXXXX. There is much more under the covers when considering authentication and pagination, but the URL I am showing is the REST call
- I then report and visualize in Power BI.
A couple of notes:
- By using a filter for determining the data I can pull the same results into a JIRA Dashboard, Confluence Page, or any other tool where this universe of data is needed.
- The right mechanism for reporting will be driven by your audience. If everyone is JIRA savvy, then you may not want to try anything external.
- Power BI (or something like it) allows you to pull information across the Organization. With the security inside of JIRA, you may find different users would get different information based on their permissions. And of course, inside of JIRA you would need to share your filters and dashboards.
- Finally, an external tool can make it easier top integrate this data with details from your HR system (for assignee details) or your change management system (for example, ServiceNow)
Here is what I ultimately came up with. Let me know if you need more detail. Thanks

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.