Hi @Timothy ,
You can't get metrics like cycle time or lead time by just using JQL because all JQL does is filtering. It does not do calculations.
On the other hand, a JQL query like below might be helpful for throughput. It fiters issues that are currently resolved or closed and was resolved in January 2019.
project = ABC and issuetype = Task and status in (Resolved, Closed) and status change TO resolved AFTER "2019-01-01 00:00" BEFORE "2019-01-31 23:59"
Yes, Kevin and Emre are right. You can get Cycle or Lead Time by using the build-in Jira Control Chart or by using additional apps, like such below:
Hope it helps,
Hello @Timothy ,
Our team at OBSS created Time in Status app for this exact need. It is available for Jira Cloud, Server and Data Center.
Using Time in Status, you can report how much time each issue spent on each status. You can choose to include, exclude or combine certain statuses so you can easily have TiS calculate cycle or lead times, along with other status times for you.
Time in Status can also calculate sums or averages of those durations, grouped by any number of issue fields you pick. For example you can set TiS to calculate average durations grouped by, let's say, year, month and week parts of resolution date so you will see something similar to this.
The report contains averages for all selected statuses and lead/cycle time columns as well. The number of issues are shown as a column as well which I suppose can serve as the throughput you are asking for.
As well as statuses, you can report how much time each issue spent on each assignee or even each user group. These are perfect for reporting on bottlenecks in your process. The app also has two level reports that show status durations broken down by assignees or vice versa.
You can produce reports based on the default 24/7 calendar or define your own business calendars with custom workdays and working hours. This is important because a report based ona 24/7 calendar does not make sense most of the time. Any issue that was opened on a Friday close to the end of business day and that was resolved early morning of next Monday will seem to be resolved in two and a half days on a 24/7 calendar which in fact is resolved in a few business hours. Custom calendars let you see that.
All data can be exported as XLS, XLSX, CSV.
Try our Great Gadgets app for Jira. It offers all the gadgets needed for calculating and displaying the throughput (Kanban velocity) and cycle/lead time (as trend chart or control chart).
In case of questions, please don't hesitate to contact us at email@example.com.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event