JQL Time in status reports

[#1]

Jira Query Language (JQL) is widely used to search for information about Time in Status in Jira. Сustomets utilize JQL queries to gain insights into issue lifecycles, track progress, and optimize workflows. 

I'm sure you use jira time in status JQL in your work as well. Today's article will remind you of common jira query time in status.

JQL queries for Time in Status also aid in performance analysis and reporting. Users can generate Jira time between status custom reports and metrics to measure team and individual performance, track progress, and identify areas for improvement. These insights support you to identify bottlenecks in Jira.

        1. Issues that have been in development per month during a year.

status changed to "In Development" during ("2021-08-01 ", "2021-08-31 ")

       2. Issues changed to the ”Closed” status between five and two weeks before my current time:

status changed to closed after -5w before -2w

       3. Issues with status "Resolved" in Service Desk Project between 01 January 2022 - 31 December 2022.

project = SD AND status = Resolved AND resolution is not EMPTY AND createdDate >= startOfYear(-1) AND createdDate <= endOfYear(-1) ORDER BY created ASC

       4.  Issues Resolved and/or Closed by a particular user

status WAS Done BY "user_name"

       5. Issues that have been in a particular status for a specific duration:

status = Open and not status changed after -2w

       6. Issues in X project with issue type x that were transitioned to status X between date and date:

Project = Negotiations AND status CHANGED TO "Accepted" and (updated >= "2022/12/26" and updated <= "2022/12/30")

       7. Issues which has historically had a status of "Ready for Deployment" and now are in status "Ready for Deployment":

Status was "ready for deployment" AND status = "Ready for deployment"

       8. Issues which has status "ready for deployment" and had status "ready for deployment":

Status was "ready for deployment" or Status = "Ready for deployment"

       9. JQL for Filter by date and status:

updatedDate >= -5d OR status != DONE

       10. JQL Resolution Time:

Resolution = Unresolved AND Status changed to "In Progress" BEFORE -5d (card colour -> yellow)

Resolution = Unresolved AND Status changed to "In Progress" BEFORE -10d (card colour -> orange) 

Resolution = Unresolved AND Status changed to "In Progress" BEFORE -15d (card colour -> red

       11. JQL Cycle Time 

You cannot calculate cycle time with basic JQL. JQL only does filtering. But it is possible with add-ons.  
_______________________

Also, for enhance your reports, I suggest you try Time in Status (developed by my SaaSJet team) with 7 types of status time reports 

Here are all of them:

• Time in Status,
• Assignee Time,
• Average Time,
• Status Entrance Date,
• Status Count,
• Transition Count,
• Time in Status per Date.

I am pleased to offer you a 30-day trial of Time in Status. Furthermore, our add-on is free for up to 10 users, allowing you to evaluate its effectiveness in your service processes.

[Geremy Santos Acosta]

Hi, i'm trying to view in the Time in Status Report only a specific issue type. How can i filter by?

[Valeriia_Havrylenko_SaaSJet]

@Geremy Santos Acosta got it! 

Unfortunately, there is no way you can find it with the native gadget, but I did it with the add-on.

I've created a Status group for Cycle time and then filtered issues by JQL inside the add-on by query issuetype = Story 

Hope it helps 😊

[Geremy Santos Acosta]

This one works! Thanks