What will be the jql query if i need lead time b/w "F4 date" and "F2 date"?

Meenakshi Manocha
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 19, 2024

I need to calculate the Lead time b/w F4 date and F2 date in JIRA

5 answers

0 votes
Valeriia_Havrylenko_SaaSJet
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
February 23, 2024

Hi @Meenakshi Manocha  👋


Welcome to the community! 

As an alternative, you can try - Time in Status for Jira, which gives you Lead Time by a Particular Period (by week, sprint, etc)

To track Jira Lead time only for a particular week or sprint, all you need is to filter issues by Sprint or choose the necessary week as a date range.

TIS 4.png

TIS 5.png


Another option can be Time Between Statuses. This add-on measures connections in the workflow, through a transition time in specific issues. 
You can count Lead Time by setting start/stop and pause statuses in the configuration manager. 

Time Between Satuses.jpg

Add-ons have a 30-day free trial versions, free up to 10 users and developed by SaaSJet as well.
Hope it helps 😌

0 votes
Bloompeak Support
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
February 20, 2024

Hi @Meenakshi Manocha

Welcome to the Atlassian Community!

If you prefer to use a marketplace app to get lead time reports, 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 Lead Time for Each Issue report.

For further details, you can have a look at Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters article and Status Time Reports How to Videos.

  • This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).
  • You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
  • Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
  • You can set different duration formats.
  • You can export reports in CSV file format and open them in MS Excel.
  • You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
  • You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a completely free solution, you can try the limited version Status Time Reports Free.

Hope it helps.

0 votes
Gizem Gökçe _OBSS_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
February 19, 2024

Hello @Meenakshi Manocha ,

Welcome to the community!

As @Bill Sheboy also mentioned, you need to use out-of-the-box solutions to get the Lead Time metric for your project. 

If you are ok to use a marketplace app for your reports, Time in Status which is developed by my team at OBSS, is the tool I would highly recommend. It is available for both Jira Cloud and Data Center.

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee

Time in Status offers two report types for your case:

The first one is Status Duration report (please see the screenshot above) which shows how much time each issue spent on each status. You can combine the time for multiple statuses by your choice to get metrics like Lead Time, Resolution Time, Issue Age, Cycle Time, etc. Report Types Status Duration Report.png

As an alternative approach, Time in Status also has Duration Between Statuses report type which shows the duration between two specific statuses. This report type also allows the user to exclude the times for "pause" statuses.

DBS 2.png   Report Types DBS.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 developer 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. 

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 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. And the app has a REST API so you can get the reports from Jira UI or via REST. Also you can export the reports in to various formats easily. 

SS4.png

Visit Time in Status to explore how our JIRA add-on can revolutionize your metrics measurement process. Enjoy a 30-day free trial to experience the full range of features

Also, if you are interested in more detailed information on how to set up metrics and use  Time in Status, please consider reading my article below. 

Revealing Operational Excellence: Identifying Bottlenecks through Metrics like Cycle Time, Lead Time

Kind Regards,

Gizem

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 19, 2024

Hi @Meenakshi Manocha -- Welcome to the Atlassian Community!

It seems you want to perform a calculation between two date fields to produce what you are calling a "lead time". 

That is not possible with the built-in features of JQL; it is not a SQL and has no ability to do this type of calculation as it is for issue searching.

Possible solutions for this capability depend on how frequently you need it:

  • If you need this one-time or infrequently, I recommend exporting the issues to a spreadsheet to perform the calculation
  • If you need this often, please try...
    • Search the Atlassian Marketplace for apps which extend the features of JQL, such as for calculated fields
    • Add a custom field for the value, and use an Automation for Jira rule to calculate it

Kind regards,
Bill

0 votes
Ankush Bora February 19, 2024

@Meenakshi Manocha: Could you share more details related to this?
What is 'F4' & 'F2' ?

Meenakshi Manocha
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 19, 2024

these are two states of project, suppose it start at F0 position and flow like changing status from F0 to F1, F2 F3 and F4

Suggest an answer

Log in or Sign up to answer