Is there a way to show the "Status Changed to In Development" in the list view of the JQL query?

Artur Cybruch May 24, 2023

Hi there, I'm curious to know if there's a way to show in the JQL query list a date when an item moved to a status like "In Development"? I want to use the data to create various Kanban charts like cycle time etc. Something like below with the date visible on the List View. Thanks

Screenshot 2023-05-24 at 15.27.05.png

5 answers

3 votes
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 24, 2023

Hello @Artur Cybruch 

As an alternative , I guess you can try Time Between Statuses or Time in Status for Jira Cloud developed by my team SaaSJet.

Знімок екрана 2023-05-25 о 00.20.06.png

Time between Statuses is the add-on, which measures connections in the workflow, through a transition time in specific issues. You can count Cycle and Lead Time by setting start/stop and pause statuses in the configuration manager. To detail the calculation conditions you should select the first/last transition to/from status.

You can customize your Cycle and Lead Time reports by adjusting the app interface fields such as: Type of Project Date range Time Format Multi Calendar (to configure non-working hours and different calendars.) This add-on also allows you to export data in XLSX or CSV formats.

Time in Status for Jira Cloud will be an option for you too if you are already switching to cloud version. you get Cycle and Lead time by setting Status Groups. You can configure it from your account at the Column Manager with the drop-down list of the statuses. A custom report can be placed on the main Jira dashboard with the special Gadget tool, and you can export data in XLSX or CSV formats.

Cycle Time.gifAdd-ons have a 30-day free trial version and free up to 10 users. 
Please, let me know if you have any questions

Hope it helps 😌

1 vote
Frederik Vantroys
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.
May 24, 2023



This isn't easy to. A few things that can be done:

- for future projects you could make one or more custom fields and use that field to keep a date when an issue transitions. But that doesn't solve the problem for already existing issues.

- In Jira Server there have been documented solutions for this by diving in the sql database data but in Cloud Atlassian environments you can't access that data.

- Something that might work :

With this plugin you could extract all data of issues to a csv file and then use excel spreadsheets to filter the data. 

Artur Cybruch May 24, 2023

It's a shame that JIRA doesn't have it out of the box and I expected that will be the answer. Azure Devops have got something called "Activated Date" which works for my case but I couldn't find an equivalent in JIRA. Thanks anyways. 

I'll have to ask my company if there's any way to export the items. 

0 votes
Emre Toptancı _OBSS_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 29, 2023

Hello @Artur Cybruch

As some others have pointed out, if you want to do this with vanilla Jira, you need to create date customer fields on your issues and modify your workflows to populate those fields in your workflow. This will give you a solution but (1) You will need to create a lot of custom fields (which is not a good idea) (2) you have to build and maintain the solution (3) It won't work for past issues.

I suggest you use a marketplace app.

If you are OK with using a marketplace app for this, our team at OBSS built Time in Status for this exact need. It is available for Jira Server, Cloud, and Data Center.  

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee

tisCloud_StatusDuration_LeadTime_with Estimates.png    tisCloud_AssigneeDuration.png

You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc. 

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per Vertical or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend. 


If you want to do things manually, Time in Status also has date reports that show the transition date TO/FROM each status.


The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company Managed and Team Managed projects for Jira Cloud.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

Gadget_AverageStatusDurationByComponent.png  tisCloud_StatusDuration_LeadTime_Chart.png


0 votes
Bloompeak Support
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 24, 2023

Hi @Artur Cybruch

Welcome to Atlassian Community!

If you prefer to use 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 Status Count and Entry Dates report to see when an issue enters a new status. For cycle time, you can have a look at Cycle Time by Assignee report, Cycle Time by Components report, Cycle Time by Project report, Cycle Time for Each Issue report, Cycle Time by Issue Creation Month report as examples.

For further information, you can have a look at the details below and  Status Time Reports How to Videos.

  • 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 Free.

Hope it helps.

0 votes
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 24, 2023

Hi @Artur Cybruch 

Welcome to the community !!

Not sure if this data is available out of the box. However if you would be interested in app, you can try out
Agile Tools : Epic Tree, Links Tree, Time in Status & Worklogs

The add-on provides the status transitions for the entire lifecycle of the issue, as in the screen grab below

There are 20+ reports in the app which help to meet a wide range of use cases plus many other use cases are covered like Hierarchy reports, worklogs reports etc.

Do try it out.

Disclaimer : I work for RVS, the vendor for this app

Transition Dates.PNG

Suggest an answer

Log in or Sign up to answer