JIRA Plugin for Lead and Cycle Time

[Niranjan Deshpande]

Looking to measure lead time, cycle time and time in/betweed status for jira issues.

Control charts are not easy to interpret. So looking to use a plugin.

Which plugin from the JIRA market place is most recommended? I have come across these two. Any recommendations/advice from the community will be helpful.

https://marketplace.atlassian.com/apps/1211756/time-in-status?tab=overview&hosting=cloud 

and

https://marketplace.atlassian.com/apps/1219732?tab=overview&utm_campaign=3_tools_to_analyze_Cycle_and_Lead_Time_in_the_Jira&utm_content=Addon_Name&utm_medium=Article&utm_source=Atlassian_Community&hosting=cloud

https://marketplace.atlassian.com/apps/1221462?tab=overview&utm_campaign=3_tools_to_analyze_Cycle_and_Lead_Time_in_the_Jira&utm_content=Addon_Name&utm_medium=Article&utm_source=Atlassian_Community&hosting=cloud

[Karolina Wons_SaaSJet]

Hello @Niranjan Deshpande 

As an alternative, you can try another add-on - Time between Statuses. It allows monitoring Cycle and Lead time easily. You can display this data both on the dashboard or export reports to Excel or XLSX files.

This add-on is developed by my SaaSJet team. Please, let me know if you have any questions.

Hope you find it helpful

[Emre Toptancı _OBSS_]

Hello @Niranjan Deshpande and @Eman Mostafa ,

This is an old post but since you are still following it, please let me respond by explaining how you can get Cycle Time and Lead Time in two different ways with our app Time in Status by OBSS. It is available for Jira Server, Cloud, and Data Center. 

Time in Status mainly allows you to see how much time each issue spent on each status and on 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. This report type has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements 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 the exclude the times for "pause" statuses.

  

These reports show a list of issues by default so you can see the metric values for each issue separately. Also, for all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total cycle time per customer (organization) 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.

Time in Status 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.

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.

  

Using Time in Status you can:

• See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
• Export your data as XLS, XLSX, or CSV.
• Access data via REST API. (for integrations)
• Visualize data with various chart types.
• See Time in Status reports on Jira Dashboard gadgets

https://marketplace.atlassian.com/apps/1211756/

EmreT

[Eman Mostafa]

@Niranjan Deshpande Can you share a conclusion about how you were able to measure the lead time and cycle time?
I have tried the jira plugins but none of them gives you one value for lead time and cycle time for every ticket, and for a group of tickets.

All these plugins provide the time between every status and the other, but no total numbers for the whole cycle time.
Can you help?

[Madhu_RVS_Support]

Hi @Eman Mostafa 

As an alternative, you can try out our plugin,

Time in Status Reports 

The add-on provides the time in each status for the entire lifecycle of the issue . And you can group the statues to define your own lead time/cycle time etc.

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

[Bloompeak Support]

Hi Emon,

You can get cycle time report by grouping statuses as in the below video.
https://www.youtube.com/watch?v=jMCFB2gitso

If you are looking for a report other then cycle time, just let me know. I will also provide the steps to generate it.

[Starware]

Hi,
You can also check "Custom Fields++" app provided "Time in Status" field. It allows you to configure how you want to monitor each status and you can write JQL queries like "In Test > 2w".

[Bloompeak Support]

Hi @Niranjan Deshpande ,

For this exact need we developed Status Time app. It provides reports on how much time passed in each status. It has the grouping of statuses functionality so that you can get cycle/lead time reports.

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. It has various other reports like assignee time, status entry dates, average/sum reports by any field(eg. average in progress time by project, average cycle time by issue creation month). And all these are available as gadgets on the dashboard too. Here is the online demo link, you can see it in action and try without installing the app.

If you are looking for a free solution, you can try the limited version Status Time Free. Hope it helps.

[Chris Boys]

Hi @Niranjan Deshpande,

Depending on the insights you're looking to generate for your team, another off-the-shelf web app alternative is our Team Performance Summary from umano.tech.

Essentially, it's a dashboard for agile teams to track how they're designing, building, reviewing and engaging in their sprint or Kanban intervals.

Within a teams' design & build flow, we provide insight into a team's speed as measured by Lead and Cycle Time. You can find out more about why this measure of your practices matters, and how we calculate it in our Guide, but essentially Umano is mapping the time from ticket creation through to resolution or done.

Here's an image of how it's displayed over multiple sprints or intervals.

You can see the full range of our measures in our Guide.

Teams value the ability to self-compare their current performance relative to their usual performance (the shaded wave pictured above, representing the rolling median for the last 6 intervals, where the breadth of the wave depicts the range of scores for each interval). 

As you can see, our predefined agile success metrics enable greater team observability not just into HOW they're practicing, but also by surfacing the underlying drivers most impacting your team's effectiveness - see the callouts of what practices are impacting the measure. These underlying drivers provide context as to why a team may be above or below it's usual rate of performance.

Interval Reports can be exported as an email.

Hope this helps!  Let me know if you have any other questions.

Chris

[Rahul_RVS_Support]

Hi @Niranjan Deshpande 

You can look at our plugin,

Agile Tools : Epic Tree & Time in Status 

The add-on provides the time spent in each status for the entire lifecycle of the issue. You can combine your statuses to define your Lead/Cycle times and also extract the transitions history of the issues. Along with various Issue stats reports, you get additional features like Epic Hierarchy, Links Hierarchy & Worklogs Report to track the project's progress. The main features of the app are as below

• More than 8 types of Time in Status Reports. Excel Export available for all status reports.
  
  • Time in Status
  • Time with Assignee
  • Time in Status with Assignee
  • Time with Assignee per Status
  • Status/Assignee Count
  • Multiple Transition Reports
  • Avg Time reports
• Epic Hierarchy / Sum Up (Standard Jira Hierarchy Epic -> Story -> SubTask)
• Link Hierarchy / Sum Up (Hierarchy based on your issue link, upto 10 level deep)
• Worklogs Report
• Timesheet Entry screen

[Fabian Lim]

Hi @Niranjan Deshpande

Try the free trials and you will know which ones meets your needs at a reasonable cost.

We had time in status in dc and it did a good job for the time in status reports, but not sure about the other kpis you are trying to report on.

Regards 

[Bill Sheboy]

Hi @Niranjan Deshpande 

Without recommending a specific marketplace addon/app, I respectfully recommend you search and test by the features you want and consider also:

• If you find using the control chart difficult, just using Lead Time and forms of Cycle Time could cause unintended side-effects and problems.  Please consider learning how to manually create and interpret such measures to better understand what they can show before trying a tool.  This book can help with that: Actionable Agile Metrics for Predictability: An Introduction, by Daniel Vacanti.
• Look for tools which can show the distribution of the data, not just things like averages (arithmetic mean).  Outlier values far from the norm could influence your results if you do not understand the distribution.
• Look for tools which allow an option to filter/show outlier values
• When a tool states that it measures "Lead Time" or "Cycle Time", ask them what they mean by those terms, and ask them to demonstrate their product actual shows them
• Take caution of vendors if they say calculating a measure is some form of proprietary formula, as that is unlikely for ideas based around Little's Law and Conservation of Flow
• If you want to perform longer term forecasting, look for tools which support models like Monte Carlo analysis

Kind regards,
Bill

[Niranjan Deshpande]

Thanks a lot for that! :)