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; } } }

status changes timestamp

shay ron

Hello,
We would like to export the status change timestamps in order to measure our progress regarding bug resolution (you can see our bug flow in the attached screenshot). I can't find a convenient and automated way to export the status change timestamps as they are documented in each item's history.

Maybe I'm missing something but, could you please guide me on how this can be done?

Thank you,
Shay

image (1).png

Accepted answers

All comments

Jim Knepley - ReleaseTEAM

Welcome to the community, @shay ron

I suspect you're looking for the "time in status" add-on or something similar.

If you're inclined, you can create your reporting using the REST API to get an issue's history and do the calculations and presentation yourself.

Depending on your exact needs, you might get some satisfaction using Automation by commenting on how long an issue is spent in a state when it leaves that state. That approach makes aggregation and reporting difficult, but might be sufficient.

Yuliia_Borivets__SaaSJet_

Hi @shay ron

You might check this article: How to capture the “date of change” for Jira issues

However, there is no easy way to export status change timestamps in Jira.

Some apps developed by my team can help to export timestamps:

Issue History for Jira allows you to get timestamps for any field change, including statuses:

timestamp for status change.png

View Confluence page and exported file sample

Time in Status allows to get a report of the Status Entrance Date:

status entrance report jira.png

If you don't use these apps, you can try them free for 30 days.

Hannes Obweger - JXL for Jira

Hi @shay ron

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.

Alternatively, there's a number of apps available on the Atlassian Marketplace that can help extracting this data for you. 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 date/time of transition to [status], time in [status], time between [status] and [status], and many, many more.

This is how it looks in action:

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

Petru Simion [Simitech Ltd.]

Hi @shay ron ,

You can only visualise the change timestamp for the status in each issue history.

In order to visualize and export multiple issues, and potentially multiple status changes within each issue, you can use Issue History Dashboard for Jira an app released by our company.

You can sort your filtered search to only display history changes where the Status field was changed, by using the Field Updated search field. You can visualize a paginated result but also export the search result to csv.

The Date of Change column will contain the date of the history change.

The Value From, Value To columns will show the values before and after the change.

Screenshot from 2025-01-07 16-54-32.png

Gizem Gökçe (OBSS)

Hello @shay ron ,

Welcome to the community!

As you've already mentioned, the required data is available in each issue's history but you will need to use a marketplace app to get ready-to-go reports. Good news that report is available in our application where you can directly learn the transition dates without having to deal with Jira issue histories. The app is Timepiece - Time in Status for Jira , the oldest and leading Time in Status app in Atlassian Marketplace, which is built by my team at OBSS. It is available for both Jira Cloud, and Data Center.

You can use the date-based reports to see the transition dates from/to a status. In the screenshot below you can see the transition dates of the issues to each status. I think this report will be spot on for your needs.

Report Types FT to Status Date.png

If you'd like to explore this solution further, feel free to check out Timepiece on the Atlassian Marketplace or schedule a demo with us for a walkthrough of the app's features.

Hope it helps!

Gizem

shay ron

Thank you all for the helpful responses. I will try using one of the suggested plugins as a starting point and proceed from there.

However, I found some fields that, based on their names, seem like they should be useful, but they are currently empty:

Change Completion Date
Time to Resolution

Is it possible that I can adjust the settings so that the relevant values are stored there?

Best,
Shay

Vitalii_Bobak_SaaSJet

Hi @shay ron

Great to hear that you're exploring solutions to track status change timestamps!

Regarding the empty fields you mentioned—Change Completion Date and Time to Resolution—these fields are typically part of Jira Service Management or custom SLA settings, and their functionality depends on specific configurations. Here’s what you can check:

Field Configuration:
- Ensure that these fields are included in the relevant screens (e.g., issue view screen, edit screen) for the project.
- Verify the field context to confirm it's associated with the issue types and projects you're working on.
Automation Rules:
- Use Jira's Automation feature to populate these fields dynamically. For example:
  - Set the Change Completion Date when an issue transitions to a specific status, such as "Done."
  - Calculate and set Time to Resolution based on the difference between issue creation and resolution timestamps.
Third-Party Apps:
- If manual configurations don’t meet your needs, apps like Time in Status can provide these insights with minimal setup.
- These apps also offer detailed reports, such as Status Entrance Date and Resolution Time, which can be exported for further analysis.

Status Entrance Date:

Знімок екрана 2024-06-24 о 23.45.28.png

Resolution Time:

Знімок екрана 2025-01-15 о 15.33.31.png

Best of luck, and feel free to reach out if you need further assistance!
Add-on Time in Status developed by my team.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-cloud

resolution