A ticket gets moved from Backlog to ToDo, Testing, Review, Done and many other status based on our project workflow. For a particular ticket, I want a filter to list the dates when a ticket was moved from ToDo to Testing, Testing to Review, Review to Done and so on.
Jira history mentions the dates whenever a ticket was updated to a new status.
How can that be done with JQL for a particular ticket? Also is it doable from JQL?
I guess JQJ for a particular ticket and specific status transitions can be something like the one below:
id = MARC-1587 AND status CHANGED FROM "ToDo" TO "Testing" AND status CHANGED FROM "Testing" TO "Review" DURING (("2023/06/10","2023/06/16"))
You might also check the following article:
JQL will always return a list of issues. If you need more detailed analytics, you can try our addon:
The add-on provides the transition dates for each status in the issue lifecycle.
You can also create a Dashboard gadget out of it with graphs too.
Also there are 20+ reports in the app which help to meet a wide range of use cases.
Do try it out.
Disclaimer : I work for RVS, the vendor for this app
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sanjog Sigdel 👋
As an alternative, you can try Time in Status for Jira Cloud (developed by my team). The primary purpose is to help teams gather valuable data about the lifecycle of your issues in Jira. Add-on allows you to measure and visualize the time spent in each status, such as "Open," "In Progress," "In Review," and "Closed," and provide 7 types of reports to help you identify areas for improvement.
One of them is The Status Entrance Date report shows the date an issue has moved to a particular status.
With this report you will get dates when the issue has entered each of the statuses on the grid as it’s shown below.
On the chart, it shows the number of tasks that have entered a status on a certain date - for example, 1 task out of 5 tasks has entered the Progress status for the first time on the 23-rd of May.
Add-on has a 30-day free trial version and free up to 10 users.
Please, let me know if you have any questions
Hope it helps 😌
Valeriia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Sanjog Sigdel
Jira does not provide this functionality out-of-the-box. JQL queries can "filter" issues but they can't make calculations and they do not show transition dates as columns in their result set. You are correct, the required data is available in each issue's history but you will need to use a marketplace app to get ready-to-go reports.
Our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center.
Time in Status has duration-based and date-based reports.
Time in Status mainly allows you to see how much time each issue spent on each status or each assignee.
You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc.
You can also use the date-based reports to see the transition dates from/to a status
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 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.
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. You can also get file exports and REST API access.
Timepiece - Time in Status for Jira
EmreT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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. Entry date (see In Development, Ready for Testing, In Testing, In Development columns.) is status transition date and status count(see #In Development, #Ready for Testing, #In Testing, #In Development columns) is how many times an issue is entered to this status.
If you are looking for a completely free solution, you can try the limited version Status Time Free.
Hope it helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank You for your response. But I'm looking for an in-house solution provided by JQL and Automation. Also I think I figured something our on my own. I'll provably write an article about it here in the community.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi sanjog im having a pretty similar problem do not want any apps or subscription
can u pls tell how u managed to solve the problem using JQL
i only want the creation and end date if completed .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sanjog Sigdel,
It depends what you are trying to do. History search in JQL lets you search for e.g. transitions that happened between certain dates, like in this example:
status changed to "Testing" after startOfMonth()
it will return all issues that have changed to status Testing after the beginning of the current month. You may want to check out this community artlicle to learn more and check out additional examples of what is possible.
At the same time, notice that JQL will always return a list of issues. To see the details and the various stages issues went through, you will need to check out the issue details.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.