Custom field for Lead distribution time report

[Andreia Lopes]

Hi,

I have created a Lead distribution time report like the one on eazyBI Demo for different issue types separately and realized that it considers the number of days taken to reach the Done status right from when the issues were created until they are are resolved. In the rows section, I placed the Resolution interval. However, most of the issues created were not picked up to work on immediately making the resolution time more than expected since time was not actuallty spent on resolving them because they were in the backlog. I need a custom field that would allow me to select from which status I want the resolution time to be calculated rather than it being calculated from the issue created date by default so that, the lead time specified by resolution intervals be accurate.

Thank you for your help!

Best regards, 

Andreia.

[Mehmet A _Bloompeak_ · Accepted solution]

Hi @Andreia Lopes

Welcome to the Atlassian Community!

What you're looking for seems to be cycle time rather than lead time. You can have a look at the article below which explains the details of cycle time & lead time and how to get these reports in Jira. Hope it helps.

Productivity Measurement with Two Critical Parameters: Cycle Time and Lead Time

[Emre Toptancı _OBSS_ · Accepted solution]

Hello @Andreia Lopes

Let me recommend our solution that provides the best flexibility. Our team at OBSS built Timepiece - Time in Status for Jirafor this exact need. 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 and on each assignee. 

       

The app 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.

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 customer (organization) or average resolution time per week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) is particularly useful here since it allows you to compare different time periods or see the trend.

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.

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

Timepiece - Time in Status for Jira

EmreT

[Bill Sheboy · Accepted solution]

Hi @Andreia Lopes -- Welcome to the Atlassian Community!

What you are describing would no longer be lead time.  Lead time is the duration from when a request is created until it is completed/delivered.

You seem instead to want some form of cycle time, measuring from one particular point (e.g. status for start of work) to another (e.g. resolved) in the workflow. 

To measure such a cycle time with out-of-the-box Jira, you could use Atlassian's interpretation of a control chart: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/

You could also investigate marketplace options for better reporting than Jira contains, or you could add a custom field to capture a point (date/time) in your workflow and set the value with an automation rule, enabling other reporting options.

Kind regards,
Bill

[Roberts Čāčus - eazyBI]

Hi @Andreia Lopes ,

You can define custom cycles in eazyBI with calculated measures. But for an interval-like representation, I recommend JavaScript calculated custom field option. The eazyBI documentation page has an example here - https://docs.eazybi.com/eazybi/data-import/data-from-jira/jira-custom-fields/javascript-calculated-custom-fields#JavaScriptcalculatedcustomfields-Cycledays.

There you will also see more details on defining the JavaScript calculated custom fields.

Let me know if you have any questions or suggestions.

Best,

Roberts // support@eazybi.com