How I can obtain the status of Jira tickets at a specified date?

[Emma Handley]

I need to create a report including all tickets created within a specified period, and the status of those tickets at the end of that period.

My problem is that Jira only appears to provide a current status. How can I obtain ticket status as at a specified date? 

Would the Timepiece - Time in Status for Jira plugin provide this functionality, or are there any other plugins that would? 

My question is for Jira Cloud, and Jira Service Management.

Thanks

[Natalia_Kovalchuk_SaaSJet_]

Hi @Emma Handley ,

Yes, unfortunately, Jira Cloud doesn't offer a built-in way to view the exact status of tickets from a specific time in the past.

If you are open to using third-party apps, I can recommend Issue History for Jira (Work Item History) from my team as a workaround. 

With it, you can do the following: 

• Filter tickets by a specific project and the required date range (or any other Jira fields).
• Add the Created and Status fields to the report.

• View the status of each ticket at the selected point in time.
• Export the results to Excel or CSV for further analysis.

[Birkan Yildiz _OBSS_]

Hey @Emma Handley 

First, welcome to the Community!

This is Birkan from the Timepiece - Time in Status for Jira team.

To answer your question directly: Yes, Timepiece - Time in Status for Jira provides exactly this functionality for both Jira Cloud and Jira Service Management.

Here is a more detailed guide on how you can build this exact historical snapshot:

Filter your scope: Use the JQL Filter to pull all the tickets created within your specified period.

 Use the Status Count Report: Select the Status Count report type.

 Apply Trim History: Under the Dates settings, use the Trim History feature and set the end date to your specific target date. This feature will trim the history of each issue, completely ignoring any status changes that happened after your selected date.

In addition, our another app, Historian – History Explorer for Jira, was built to address these kinds of needs.

With it is ''Historic Query'' feature, the app features a specific Historic Query tool designed exactly for this use case, allowing you to see the exact state of your issues at any given point in the past. You can learn more about how it works by reading my Atlassian Community article. If you'd like to learn more about Historian, here's its Atlassian Marketplace page.

You can find Timepiece - Time in Status for Jira and on the Atlassian Marketplace, too.

Best,
Birkan

[Joseph Chung Yin]

@Emma Handley -

I would recommend that you create a custom field with automation rule to control the population of it based on when issues move into the specific status.

A few things you need to consider -

1) Once an issue moves into the specific status, can the same status be moved from all other statuses in your WF.  If you have setup where every status can moves into the specific status, then you need to ask when you want to capture the time information?

2) In the automation rule, you can also set it up so the custom field can be populated only once and cannot be updated again.  This way if the initial moves into the status is the key focus, then you will have your data that you needed.  If the initial population of the custom field is important to you/your team.

Afterward, you can use JQL to report against on the custom field.

Alternatively, third party add-ons may assist you...

Example - https://marketplace.atlassian.com/apps/1223898/dashboard-hub-pro-charts-reports-time-in-status-for-jira?hosting=cloud&tab=overview

Hope this also helps.

Best, Joseph

[Rahul_RVS]

Hi  @Emma Handley 

You can use Jira Rest Api's to pull this information and build your own custom solution.

However if you need detailed reporting to track changes for multiple issues, you may want to have a look at a mktplace app for the same.

We have built an app to extract changelog data in a simple and easy to use interface. The data can be exported to a CSV file as well.

It provides complete details of when the status changed and by whom.

Issue History Reports

Do give it a try.

Disclaimer : I am part of the app dev team

[Viswanathan Ramachandran]

Hi @Emma Handley 

Seems like a well-known limitation. Jira doesn’t support point-in-time reporting columns out of the box, however you can approximate or come close enough using custom JQL or Jira Automation. 

• Try the JQL like and export them separately to get the status of each ticket. Ex:

created >= "YYYY/MM/DD" AND created <= "YYYY/MM/DD" AND status WAS "In Progress" ON "YYYY/MM/DD"

• Try Jira automation time stamping if for recurring reports
  • Create new custom field
  • Set up a scheduled automation rule to run on the exact end-date of your period.
  • Have the rule copy the {{issue.status.name}} into your custom field for all issues matching your creation period.
• Timepiece (Time in Status) is fine and primarily known for calculating durations (e.g., How long was this in Dev?), it includes historical snapshot capabilities. In Timepiece, you can configure a Status History Report, select your date range, and view the precise state of your workflow transitions at that specific moment.
• As an alternative, 3rd party apps like eazyBI Forecasting and Reporting and Custom Charts for Jira can do this for you. May be Power BI connector can help too. 

[Gabriela - LeanZero]

Hi @Emma Handley, you don't need an app to read status back at a date. Viswanathan's JQL is the one to run, though the date window in it will cost you a day.

project = ABC AND created >= "2026/04/01" AND created < "2026/07/01" AND status WAS "In Progress" ON "2026/06/30"

A date with no time component is read as midnight, so created <= "2026/06/30" stops before anything raised during the 30th itself. Closing on the next day with < keeps those.

Name real statuses in the WAS clause too. statusCategory won't work there, the operator only takes Assignee, Fix Version, Priority, Reporter, Resolution and Status. From there it's one run and one export per status, and those stack into the per-ticket table you described. Same in a JSM project.

ON works at day granularity, so a ticket that moved on the 30th can show up in two of those exports.

https://support.atlassian.com/jira-service-management-cloud/docs/jql-fields/

[Duc Thang TRAN]

Hello  

I suggest using the REST API changelog (/rest/api/2/issue/{issueIdOrKey}/changelog) as the main source. If you are not familiar with Python, you can also ask an AI assistant to help you build the extraction logic.

The proposed approach is to determine the ticket status for a selected date and time by checking the status changelog. If there is a status change on or before the selected timestamp, use the most recent one. If there is no status change before that timestamp, assume that the ticket was still in its initial status, meaning the status before the first recorded change.

Then be exported to Excel, including an Issue Key column to make a pivot table 

[Alvaro Aparicio]

I think there are some alternative plugins. If you want a spreadsheet layout where you could pick a date and see a column with the exact status of each ticket on that day, consider these alternatives:

-JXL - Jira Sheets & Issues Editor: It natively includes built in "History Columns" that let you display the status on any specific date seamlessly alongside your fields.

-Issue History for Jira: Designed purely to track historical changes across multiple tickets. It allows you to select a specific date range, filter by creation date, and explicitly look at the exact status transitions during that timeframe in a clean table format.

I found this thread which could help you too

Hope it helps.