System Lead Time

[paulo.kolbe]

Hi guys,

I’ve built easily a Customer Lead Time (From Idea to Done) using Resolution Intervals and Measures.Issue Resolved Dimensions but I can’t manage to build a System Lead Time (From To do to DONE).

Please, could you give some tips for building a System Lead Time report?
Basically, I can’t set a different initial status for characterizing a System from a Customer Lead Time.

Obs. Imagine my worflow like this: Ideia > Analyze > To Do > Dev > Test > Done.

Thanks in advance

[gerda.grantina]

Hi @paulo.kolbe ,
In our eazyBI demo report you can get some ideas for calculated measures (it contains different ways on how to create lead and cycle times): Average lead and cycle time - Issues - Jira Demo - eazyBI

See also some examples in other community answers:

Calculate Lead/Cycle Time From Specific Statuses

You would like to check out our example reports in our demo accounts for Cycle and Lead times. We set a dashboard Age Lead, and Cycle Time there to represent different cases. Here are some measures I would like to point as examples: Cycle time for a specific set of statuses for resolved issues and measure Rolling average cycle time in particular. This measure contains two approaches. The formula by default works for any statuses in status category In Progress. There is an alternative solution …

Average Lead and Cycle Time Report

Hi Mike, You would put the Time Weekly hierarchy on rows. Note that there is a dynamic calculation of the Last 4 weeks available that you can select and drill into to always see the latest four weeks. Then, about the Measures (you can read more about the below measures in the same above link): Issues created - groups issues on Time by their creation date. So this would show how many issues are created within the specific week. Issues started - you can get this by combining ‘Transitions…

best,
Gerda // support@eazyBI.com