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

Management is looking to add a date difference column

Naresh Rajak

Hello,

that shows how many days since status was first changed to 'In Progress'.

I am new and has not used J Query. Keen to learn if the solution requires using J Query.

Simple solution is preferred.

Thank you for taking time to read. Please help.

Regards

Naresh

Accepted answers

All comments

Benjamin_tmh9yg

HI @Naresh Rajak ,

There isn't an out of the box solution that is tracking the counter. You may want to check Atlassian marketplace apps. Looks for key words like "status and time". Usually, you can trial apps for 30 days to see if it serves the purpose you need.

-Ben

Bill Sheboy

Hi @Naresh Rajak

That measure is sometimes called the "Age of WIP", and there is nothing built-in to measure it.

There are marketplace apps for such time-in-status tracking (reading the information from the issue history). Or you could use custom fields and an automation rule to help.

For example, let's assume an issue never has "backwards flow", to return to a "To Do" status once it is "In Progress". In that case, using the statusCategoryChangeDate value one may use a scheduled trigger rule to calculate the value:

https://community.atlassian.com/t5/Automation-questions/Hi-community-nbsp-nbsp-How-about-Age-of-WIP-work-item-age-1/qaq-p/1561072/comment-id/12504#M12504

When "backwards flow" can happen, the first transition to an "In Progress" type status may be saved in another variable (or entity property) and used for later calculations. This would require an additional rule.

Kind regards,
Bill

Petru Simion [Simitech Ltd.]

Hi @Naresh Rajak ,

An automated solution using custom fields will only work from the moment the solution has been implemented, leaving you with your other issues uncalculated.

The issue history tab will reveal the first time the issue was transitioned into status In Progress as well as the date.

One can calculate the difference.

However if you need to deal with multiple issues, and are open to apps you can use Time in Status Dashboard for Jira , an app released by our company.

When the issue is moved into status In Progress, and while the issue is still in that status, the app will display the time since the issue was transitioned into In Progress and the date the search is done.

If the issue is later transitioned out of status In Progress into another status, the app will show how long the issue spent in status In Progress.

If the issue is transitioned later again into In Progress, the app will display the total time spent in the status, and also will display how many times the issue was in the status.

You can select to see the result in two perspectives.

Columns Perspective

Rows Perspective

Search result can be exported to csv.

Regards,

Petru

Hannes Obweger - JXL for Jira

Hi @Naresh Rajak

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 time that an issue spent 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 time in [status], time between issue creation and [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

Ayça Erdem_OBSS_

Hi @Naresh Rajak

Welcome to the community

An issue’s status changes are logged in its issue history, which can be accessed from the issue view in Jira or through Jira’s REST API. While it’s possible to track and calculate the number of days an issue has been in a specific status manually, this process can be quite tedious and complex.

To simplify this, many teams use dedicated Atlassian Marketplace apps that automate these calculations. One such solution is Timepiece - Time in Status for Jira, developed by my team at OBSS. Timepiece helps track how long issues have been spent in each status, and how many days have passed since a transition, and provides flexible reporting options. With built-in visualizations and export capabilities,

For your specific use case, the Status Duration Report in Timepiece would be a great fit. This report shows exactly how long issues have remained in each status, including the total time spent in In Progress. By filtering the report to focus on this status, you can easily see the number of days since an issue first transitioned. Additionally, the report offers chart views to visualize trends over time.

Here is an example of the Status Duration Report

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

Ayça

Valeriia_Havrylenko_SaaSJet

Hi @Naresh Rajak

If you’re open to using add-ons, it is possible to show how many days since status was first changed to 'In Progress' with Time Metrics Tracker | Time Between Statuses

Here’s how you can achieve this:

1. Create a new metric: Work in Progress Time (from Created to Resolved).

2. Define your work schedule, e.g., Monday–Friday, 9 AM–5 PM.

Знімок екрана 2025-02-08 о 00.40.02.png

3. Additionally, with the add-on, it is possible to measure metrics precisely by selecting the transition statuses you need to calculate this metric. This ensures that your reports will be highly accurate.

Also you can book a session with our specialist to see add-on in action 🚀

Add-on developed by my SaaSJet team.
Hope this helps!

Mehmet A _Bloompeak_

Hi @Naresh Rajak

As far as I understand, what you are looking for is a cycle time (the time it takes for the team to start working on an issue and complete it) report. The raw data you need is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning a json which you need to parse to calculate cycle time.

If you prefer using a marketplace app, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app. For your case, you can have a look at Cycle Time for Each Issue report. You can choose the statuses that you want to include in cycle time calculation.

For further details, you can have a look at Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters article and Status Time Reports How to Videos.

App Features:

This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
You can set different duration formats.
You can export reports in CSV file format and open them in MS Excel.
You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a completely free solution, you can try the limited version Status Time Reports Free.

If you have any questions, feel free to schedule a call with us.

Hope it helps.

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-cloud