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 where you can list a set of specified statuses. Please take it into account. There are two places in the formula you would like to update for this alternate solution.
Lead time typically includes time from Issue creation till resolution. Our default measure Average resolution days represents this concept of Lead time. If you would like to use any other dates for Lead time calculation, you can start with Min resolution days or Max resolution days calculations. Those calculations work on two dates. You would like to substitute dates and switch aggregator Min/Max to Avg, as well.
You can use any set of dates in the formula. If you have some issue custom date field imported as a property, you can use it in the formula.
You can also use some dates representing value changes. Here I used the last date when a priority was set to any issue and Issue resolution date:
CASE WHEN [Measures].[Issues resolved] > 0 THEN
CASE WHEN [Measures].[Issues resolved] > 0
[Measures].[Transition to last timestamp],
eazyBI enables change history import for Priority (issue type, resolution, status, Sprints) by default. You can enable this for select lists with single values as well. You would like to address the field you would like to analyze for changes as a member of the dimension Transition field in a tuple with some historical measure.
Daina / firstname.lastname@example.org