Would like to get some details on the calculations for Cycle time, lead time.

[Pooja]

Would like to get some details on the calculations for Cycle time, lead time. What are the kind/pattern of date fields my board should have. Currently I see created,updated, start date and pattern created date. would these dates help me in analysing the cycle time, lead time etc.

[Mariana_Pryshliak_Saasjet]

Hello @Pooja 

You can try a built-in solution - Control Chart, which allows you to evaluate Cycle Time and Lead Time of your project.

Also, Time in Status for Jira Cloud and Time Between Statuses becomes handy in this case.

Time in Status for Jira Cloud lets you get Cycle and Lead time by setting Status Groups. You can configure it from your account at the Column Manager with the drop-down list of the statuses. A custom report can be placed on the main Jira dashboard with the special Gadget tool, and you can export data in XLSX or CSV formats.

Time between Statuses is the add-on, which measures connections in the workflow, through a transition time in specific issues. You can count Cycle and Lead Time by setting start/stop and pause statuses in the configuration manager. To detail the calculation conditions you should select the first/last transition to/from status.

You can customize your Cycle and Lead Time reports by adjusting the app interface fields such as:

-Type of Project

-Date range

-Time Format

-Multi Calendar (to configure non-working hours and different calendars.)

This add-on also allows you to export data in XLSX or CSV formats. If you have any additional questions, I'm here to help you:)

[Emre Toptancı _OBSS_]

@Hello @Pooja ,

The Control Chart which is available in Kanban Board reports, provides a high level solution for such cases. You don't have to create any date fields since all the data you need is already available in Jira issue's histories and Control Chart uses this data. Using the control chart you can select board columns to include in the report and get a overall summary of how much time issues spend in each column (or columns). See this page for Control Chart documentation.

I believe Control Chart has a lot of downsides:

• Lack of control over reporting details
• Inability to work with individual issues or statuses
• Not being able to get the data

Even so, if might be enough if you just need a high level picture of things.

Another custom solution is possible using custom date/number fields and automation rules but I believe it is hard to build, hard to roll out and hard to maintain. You can find details about this solution in the community as well. (See this post as an example)

For a ready built solution that offers great fexibility and details, our team at OBSS built Time in Status app. It is available for Jira Server, Cloud and Data Center.

Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee as well as entry/exit dates for all statuses. You can calculate averages and sums of those durations grouped by issue fields you select. (For example see the average InProgress time per project and per issuetype). You can also combine statuses into consolidated columns to see metrics like Cycle Time or Lead Time.

The app calculates its reports using already existing Jira issue histories so when you install the app, you can get reports on your past issues as well.

The app has Custom calendar support which means you can get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)

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 issuetype.)
• Export your data as XLS, XLSX or CSV.
• Access data via REST API.
• Use one of various chart types.

Timepiece - Time in Status for Jira

EmreT

[Mehmet A _Bloompeak_]

Hi @Pooja ,

You can use Status Time app.

If you are looking for a free solution, you can try Status Time Free.