nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I generate a report

Moheb Hedayat

Hi Team,

We are in the process of transitioning away from EaziBi, and I would like to know how far back we can generate reports.

For instance, with EaziBi, we can generate reports for all tickets (incidents/requests) from 2018 to 2025. However, I am currently only able to view reports from the past year.

Thank you!

Accepted answers

All comments

Tomislav Tobijas

Hi @Moheb Hedayat ,

If we are talking about native reports in JSM (whether custom or default ones), these usually go up to 1 year in the past.

If you would like to generate some more advanced reports via Marketplace apps. I think apps like Custom Charts and a few others support all time option.

As for some native solutions, I think that Atlassian Analytics does the trick but that's only available on Enterprise plans.

Cheers,
Tobi

Alina Chyzh_Grandia Solutions

Hi @Moheb Hedayat

In Jira it’s definitely possible to work with historical data going back to 2018. To do this, you can consider using custom charts available in Report Hub - app developed by our team.

It allows you to combine different chart types - bar, line, area, and scatter - to effectively visualize various aspects of your data for any time range. You can also apply various settings to tailor the report to your needs.

Additionally, you’ll receive real-time updates, so your reports always reflect the latest data.

Best,

Alina

Screenshot 2025-03-26 at 15.05.45 (1).png Screenshot 2025-03-26 at 15.06.38.png

Eduardo Anflor - MindPro

Hi, @Moheb Hedayat

Welcome to the community!

It depends on what data you plan to refer from more than one year back. Jira native reports usually go 1 year, and EazyBi can go further, but since you are looking for another tool, I would recommend Mindpro Graphy. I work at Mindpro, and I believe this tool can help you meet your main needs.

The app allows everyone to create dashboards very quickly, and it offers over 50 gadgets to choose from (including custom and asset gadgets). You can share the dashboards internally or with customers via the portal.

The internal dashboards have a main filter you can use to bring data from all time or a specific period. Most gadgets allow counting the issues based on the filter, and other gadgets limit the displayed data as per the user selection (pre-defined). The internal dashboards are interactive, which means you can filter the entire dashboard just by clicking on a chart segment, for example.

Screenshot 2025-02-13 at 14.41.32.png

Screenshot 2025-02-17 at 14.05.41.png

You can also add the gadgets to a standard Jira Dashboard and filter them individually using a JQL or basic filter.

I hope that helps.

Regards,

Eduardo

Danut M _StonikByte_

Hi @Moheb Hedayat,

What reports are you referring to, more exactly?

If I look at the Control Chart report of Jira Cloud, it allows any time range.

But if I look at the Resolution Time Report, it allows up to 300 days

I think some Jira reports are limited, while some others are not. So it depends on what reports you need.

As advised already, it might be better to look for an app (plugin) on Atlassian Marketplace that provides the reports and/of dashboard gadgets and has no limitations like the Jira's reports.

In case you consider the idea of using an app, have also a look over our Great Gadgets app. It offers all you need for tracking your JSM projects in an effective and easy way, and has no limits when it is about time-range used.

See this article to make an idea: https://community.atlassian.com/forums/App-Central-articles/An-effective-dashboard-for-Service-Desk-and-Customer-Support/ba-p/2360369

Danut.

[Email removed as it is against community guidelines ]

Valeriia_Havrylenko_SaaSJet

Hi @Moheb Hedayat 👋
Welcome to the Community!

It depends on what kind of data you're looking to report on from more than one year back. Jira provides a variety of built-in reports, but most of them have limitations when it comes to historical data.

For example:

Control Chart and Cumulative Flow Diagram (used in Kanban boards) usually display up to 1 year of data.
Sprint Reports, Burnup, and Velocity Charts are limited to recent sprints (and won't show historical metrics if those sprints are closed long ago or purged).
Created vs. Resolved and similar reports often rely on issue creation/resolution dates, but don’t break down status time or give insights on workflow duration.
Jira itself does not store time in status data in a reportable field, so tracking how long issues spent in different statuses over multiple years isn’t possible natively.
and while EazyBI can access longer histories, since you're looking for another tool — I’d recommend trying Time in Status

💡 With Time in Status, you can:

Generate reports for your entire Jira history (e.g., from 2018 to 2025), as long as the issue history exists.
See how long each issue spent in each status (e.g., In Progress, QA, Waiting for Customer, etc.)
Track and compare key metrics like Cycle Time, Lead Time, Resolution Time, Assignee Time, and more.
Export the data to CSV/Excel for further use.
Apply filters by project, issue type, JQL, assignee, date range, and more.

If you're currently seeing only a limited timeframe, it’s likely related to filtering settings in the app — feel free to reach out and we’ll gladly help you configure the report to display the full data range.

Let me know if you’d like a walkthrough or have specific use cases in mind!
Add-on developed by my team.

Ayça Erdem_OBSS_

Hello @Moheb Hedayat

Welcome to the community

What kind of data are you trying to report on, and how do you like to visualize it? I can offer a solution.

Timepiece - Time in Status for Jira, developed by our team at OBSS, retrieves data directly from Jira issue history. This means you can generate reports for your entire Jira timeline — as far back as your issue history goes. So, reports covering 2018 to 2025 are absolutely possible, provided that the issue data still exists in your instance.

Here are some of the key report types available in Timepiece:

Status Duration Report – See how long issues spent in each status (e.g., In Progress, QA, Done).
Assignee Duration Report – Track how long issues stayed assigned to each user.
Status Count Report – Count how many times each status was visited.
Transition Count Report – Measure how many times issues transitioned between statuses.

You can also:

Filter by project, issue type, assignee, date range, and JQL.
Export data to Excel/CSV.

If you're currently only seeing data from the past year, this is most likely due to a filter or date range setting in your current report configuration. Feel free to share the report type you're trying to build and we'd be happy to help you get the full historical view.

If you'd like to explore this solution further, feel free to check out Timepiece on the Atlassian Marketplace.

Hope it helps

Ayça

Petru Simion _Simitech Ltd__

Hi @Moheb Hedayat ,

Deppending what reports you need to be creating, if you are open to using apps, you cn use one of these apps released by our company.

Some of these apps will allow you to create reports about your configurations across your organisation and some about the data (issues)

Issue History Dashboard for Jira
- Issue history search and display. Visualize and analyse issue history to avoid bottlenecks. Export history to csv
Time in Status Dashboard for Jira
- Time in Status. Report time in status, time spent in status, times in status, how many times issue was transitioned in status
Fields Dashboard for Jira
- Visualize field to project, fields to projects, field in project, fields in projects. Find fields in screens and workflows
Versions Dashboard for Jira
- Visualize Your Organization's Versions Structure. Versions in organisation. Versions in projects. Versions across projects
Roles Dashboard for Jira
- Visualize Your Organization's Role Structure. Roles across projects. Roles in projects. Users in roles. Groups in roles

Regards,

Petru

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management