what can we do to improve to calculate the lead time from start develop until the product release?

[Nicolas Andika]

so i want to calculate how much the lead time from the development process until deployment in 2 different project, what we can do from jira to improve this calculation, i have eazyBI also to help calculate data

[Valeriia_Havrylenko_SaaSJet]

Hi @Nicolas Andika   👋

Alternatively, try - Time in Status, which gives you Lead Time by a Particular Period (by week, Sprint, etc.)

To track Jira Lead Time for a specific week or sprint, you can filter the issues by sprint or choose the necessary week as a date range.

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 configuring start/stop and pause statuses.

Add-ons have 30-day free trial versions, free for up to 10 users and developed by SaaSJet.

Hope it helps 😌

[Amay Purohit_RVS]

Hi @Nicolas Andika 

As an alternative, if you are fine with another mktplace app, you can try out 

Time in Status Reports 

The app allows to group your statuses which will help you define your own lead/cycle/resolution times easily.

Another report which might be helpful is the Time between status transitions. You can define your "from status" to "to status" to calculate the time between them.

More details here

Do try it out.

Disclaimer : I work for RVS, the vendor for this app

[Danut M _StonikByte_]

Hi @Nicolas Andika

Our Great Gadgets app offers some gadgets that will help you measure the lead time in an efficient and effective manner.

Control Chart gadget - displays the issues by their lead time in a plot-chart. You can hover individual issues to see details about it, including the lead time. It allows you to set a threshold to easily identify the outliers  - the ones in red-color that took longer than expected

Cycle Time Trend gadget - let's you visualize the average lead time for past intervals and the trend, to see if you team improves over time

Lead Time Histogram - displays the distribution of the lead time and let's you see how many issues took longer than expected 

See these gadgets explained in this article: 

https://community.atlassian.com/t5/Jira-Software-articles/Building-a-powerful-Kanban-dashboard-in-Jira-with-Great-Gadgets/ba-p/1664331

Hope this helps. If you have questions, please contact us at support@stonikbyte.com.

Danut.

[Mehmet A _Bloompeak_]

Hi @Nicolas Andika

As an alternative, 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, resolution 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.

If you have any questions, feel free to schedule a demo with us.

Hope it helps.

[Martins Vanags - eazyBI]

Hi @Nicolas Andika ,

Since you mentioned you have eazyBI already, please check our demo account page: https://eazybi.com/accounts/1000/dashboards/7513-age-lead-and-cycle-time

In eazyBI, you can define custom cycles to calculate time in the cycle (between certain jira statuses). Check out more about cycles here: https://docs.eazybi.com/eazybi/data-import/data-from-jira/issue-cycles

Then, use these cycles in report calculations to calculate the average time issue spends in this cycle.

Martins / eazyBI support team.

[Gizem Gökçe _OBSS_]

Update on May 9th, 2024: Time in Status by OBSS was recently rebranded as Timepiece. It is still the same capable app with the same dedicated team behind it. The answer below mentions the app as "Time in Status" but you can find the app in the marketplace as "Timepiece (formerly Time in Status)". 

Hello @Nicolas Andika ,

There is no built in solution in Jira for this. So in order to track the time spent in between statuses I suggest you use a marketplace app. 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 to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc. 

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.

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.

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. This means you can export data into your easyBI environment easily by using the REST API.

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.

If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Lastly, if you need further information about metrics like Lead Time and how to calculate them via Time in Status I suggest you read my article on Atlassian community. It is a 5 minute read. 

I hope you will benefit from it.

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

Gizem