Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Report Showing quantity of a status

Brad Schultz
Contributor
August 6, 2025

Our design team uses a Status "Preflight" and I am trying to create a report showing how many times an issue has been placed into that Status.  One issue could have been in that status several times in just one day.  Would like to create a report showing the amount of issues using that status.  

6 answers

1 vote
Hannes Obweger - JXL for Jira
Atlassian Partner
August 10, 2025

Hi @Brad Schultz

an issue's status changes are captured in an issue's issue history, which you can access from the issue view in Jira or via Jira's REST API. From these status changes, you can calculate the number of times that an issue has been in a particular status - however it can be quite tricky to do that by hand.

That's the reason why a lot of users rely on solutions from the Atlassian Marketplace to do that for them. E.g., you may want to have a look at the app that my team and I are working on: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a long list of so-called history columns that aren't natively available, including the number of times in [status], time in [status], time between [status] and [status], and many, many more.

This is how it looks in action:

number-of-statuses.gif

As you can see above, you can easily sort and filter by your history columns, and also use them across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting. Of course, you can also export your data to Excel or CSV in just two clicks.

Any questions just let me know,

Best,

Hannes

1 vote
Rahul_RVS
Atlassian Partner
August 7, 2025

Hi @Brad Schultz 

You can use Jira Rest API's to pull Issues change history and build you own custom solution, or a readily available solution, you might be interested in a mktplace app,

Time in Status Reports 

The "Status Count" report in the app can help meet your requirement to show how many times the issues went into eash workflow status. Also the app has 20+ reports to meet a variety of use cases.

Do give it a try.

More details here.

Disclaimer : I am part of the app team for this add-on

TIS - Count.PNG

0 votes
Petru Simion _Simitech Ltd__
Atlassian Partner
August 7, 2025

Hi @Brad Schultz ,

 

If you are open to using apps you can use Time in Status for Jira , an app developed by our company.

You can filter by various criterias, and you can view, sort and export to CSV your search result that comes in two perspectives, both disclosing how many times the issue was in each status.

 

Columns - Perspective

time_in_status_columns.png

 

Rows  - Perspective

time_in_status_result_rows.png

 

Regards, 

 

Petru

0 votes
Birkan Yildiz _OBSS_
Contributor
August 7, 2025

Hey @Brad Schultz 

While this data is available in the Jira issue history, generating a proper report from it requires a third-party reporting tool.

The good news is that the report is available in our application, Timepiece - Time in Status for Jira. With the app, you can directly learn the status counts without having to deal with Jira issue histories.
You can select your 'Preflight' status, and the report will instantly show you a list of issues and the exact number of times each one has entered that status.

statuscountreport.jpg

 

To take it a step further, you can also:

Automate it: Use our Scheduled Reports feature to have this count report automatically delivered to your team on a regular basis.

Get Proactive Alerts: With the Alarms function, you can set a rule to notify you if an issue enters the 'Preflight' status more than a set number of times (e.g., more than 3 times), helping you catch potential issues early.

Timepiece works with your existing Jira issue history, so there’s no need to change your workflows or add anything extra after installing the app. You can even generate reports for past issues right away. Reports are accessible through the reporting page, dashboard gadgets, and issue view tabs, available as both data tables and charts. Timepiece also supports CSV and XLS exports and offers a REST API. And it is available for both Jira Cloud and Data Center.

You can check Timepiece - Time in Status for Jira out on the Atlassian Marketplace. Hope this helps you get the report you're looking for!

Full disclosure, I'm on the team that makes Timepiece - Time in Status for Jira.

0 votes
Janis Plume _eazyBI_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 6, 2025

Hi,

 

If you might consider purchasing an app, eazyBI reports and charts for Jira could help.

There are standard elements in eazyBI to count status transitions and you can have a report like this out of the box:

 

Pasted_Image_07_08_2025__09_45.jpg

 

Kindly,

Janis, eazyBI support

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 6, 2025

Hi @Brad Schultz 

Short answer: there is no built-in way to count those, although there are several workarounds possible depending upon your frequency of need and willingness to spend money / time.

 

On to the workarounds:

  • need one time for one work item
    • look at the changelog / history for the work item and count them
  • need often, and have money to spend
    • investigate marketplace apps to help visualize / report on the changelogs
  • need often, and have time but no money to spend
    • There is a REST API endpoint to get the change logs, but uses paging of up to 100 change entries.  And so if a work item changes often, getting the information is challenging.  Some workarounds for that are...
      • Build an automation rule inside of Jira, triggered on transitioning a work item to that status, and increment a counter in a custom field
      • Assume there are fewer than 100 work item changes, and use an automation rule to call the REST API and count what you find for the status transitions
      • Build an automation rule in Jira which uses recursion to read the change log with the REST API (paging as needed) and perform the counts.  This is risky as the looping service limit could halt the rules for the site.
      • Build an app outside of Jira which can call the REST API and handle paging to perform the counts

 

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events