Forums

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

Query to identify when an item moved from TODO state into any next state.

Lize Gersbach
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 3, 2022

I would like to create a report with JQL, but one of my field must be when the item was first worked on , thus either added to a sprint for the first time or moved from a 'to do' state into any next state. The fields i need to use must be out of the box.   Any ideas on how to do find that type of date?

 

5 answers

1 vote
Yuliia_Borivets__SaaSJet_
Atlassian Partner
February 7, 2022

Hi @Lize Gersbach 

There are some solutions I'd like to suggest:

1. You can see when an item is moved from state to state with the history option in the activity section.

How to find issue (ticket) history status.png

To make a report you can try to export the data via REST API.

2. With the Issue History for Jira plugin you can add any field to the grid and get the report you need. My team has developed it as a journal for every past activity. So, you'll get the info when the status was changed. You can filter by project, sprint, date range.

how to get issue history for status changes.png

3. Time in Status for Jira Cloud is equipped with Status Entrance Date report. It shows the date and time when the issue was moved to each state.

status entrance date.jpg

It is developed by my team, so let me know if you have any questions.

0 votes
Rahul_RVS
Atlassian Partner
February 7, 2022

Hi @Lize Gersbach  

If you are ok with a marketplace app to get this data you can try out our app.

Time in Status Reports 

The add-on provides the date when issue was transitioned to different statuses. Also it provides the time in each status for the entire lifecycle of the issue and you can filter by issue type as well. You can also combine your statuses to define your lead/cycle/resolution time and also extract the transitions history of the issues. The main features of the app are as below

  • Multiple Time in Status Reports. Excel Export available for all status reports.
    • Time in Status
    • Time with Assignee
    • Time in Status with Assignee
    • Time with Assignee per Status
    • Status/Assignee Count
    • Multiple Transition Reports
    • Avg Time in status reports
    • Status Change Dates Report
    • Time in Status Per Time Grain
    • Time with Assignee Per Time Grain
  • Status grouping
  • Save your reports
  • CSV Export
  • Multiple chart types
  • Dashboard Gadget

Disclaimer: I work for RVS, the vendor for this app, and I am one of the developers of the app.

TIS- Status Transition Dates.PNG

0 votes
Emre Toptancı _OBSS_
Atlassian Partner
February 7, 2022

Hello @Lize Gersbach ,

Jira keeps issue changes in each issue's history (that you can see in the History tab on issue view screen) but this data is not available on a Jira field or as an out-of-the-box report.

 

Our team at OBSS built Timepiece - Time in Status for Jirafor this exact need. It is available for Jira Server, Cloud, and Data Center. 

Time in Status has 4 types of Date Reports that show the First/Last transition date From/To each status.

tisCloud_FirstTransitionToStatusDate_Report.png

Additionally Time in Status allows you to see how much time each issue spent on each status and on each assignee. 

tisCloud_StatusDuration_LeadTime_with Estimates.png  tisCloud_AssigneeDuration.png     

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 customer (organization) or average resolution time per week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) is particularly useful here since it allows you to compare different time periods or see the trend.

tisCloud_StatusDuration_LeadTime_Average_TimeGrouped.png

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.

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.

And the app has a REST API so you can get the reports from Jira UI or via REST.

Gadget_AverageStatusDurationByComponent.png  tisCloud_StatusDuration_LeadTime_Chart.png

Using Time in Status you can:

  • See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
  • Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
  • Export your data as XLS, XLSX, or CSV.
  • Access data via REST API. (for integrations)
  • Visualize data with various chart types.
  • See Time in Status reports on Jira Dashboard gadgets

Timepiece - Time in Status for Jira

EmreT

0 votes
Sachin Dhamale
Community Champion
February 6, 2022

@Lize Gersbach 

By Default Jira does not provide this feature as transition date is not store in any field so you can not see it on the report form. 

Transition date and time you can see it in the issue history or transition tab of the issue. but it will be on individual issue.

Workaround -  like @Mikael Sandberg  mentioned you need to store that transition date in some custom field using script or some automation. - You can write custom field update script which will update the date in that custom field when issue move from TODO to next status in the postfunction.

Then you can use that custom field in the report or issue navigator.

For existing issue you can also write script which will process existing issue and take the transition date from the issue transition history and update the custom field with that date and then you can see that date in the issue navigator.  

Let me know if you have any queries.

Thanks,

Sachin

0 votes
Mikael Sandberg
Community Champion
February 3, 2022

You would have to use a custom field to set the date when the issue moved out of the ToDo status. You can use an automation to set the field when the transition happen, and once you have the field set up you can use that in your report.

Lize Gersbach
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 3, 2022

Thanks for this. Not what I was hoping for.

Suggest an answer

Log in or Sign up to answer