Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,553,368
Community Members
 
Community Events
184
Community Groups

JQL for Time in status reports

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 them in your work as well. Today's article will remind you of common queries so that you remember to check them.

giphy

JQL queries for Time in Status also aid in performance analysis and reporting. Users can generate custom reports and metrics to measure team and individual performance, track progress, and identify areas for improvement. These insights support data-driven decision-making, resource allocation, and process refinement.

        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

       3Issues 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 

Status was "ready for deployment" = "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. And here was a 9 most common JQL that can help you with your reports. I would like to ask you to become editors of the article and add your most frequently used JQL in the comments. 

giphy

Also, for enhance your reports, I suggest you try Time in Status for Jira Cloud (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 for Jira Cloud. Furthermore, our add-on is free for up to 10 users, allowing you to evaluate its effectiveness in your service processes.

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events