Hi,
I want to create report in which i want to show the average number of days took by any ticket to reach from status “Priortized” to status “Ready to deploy”.
And the important thing is, ticket will be moved to priortized first during the start of the sprint and will be transitioned to some other statuses as well and will finally reach to status “Ready to deploy”.
Is it possible to create such kind of report in eazyBI?
1)To calculate the average number of days it takes for issues to go from first entering “Prioritized” status to their final completion in “Ready to deploy” status, you will need to create a new calculated measure following the formula below:
AVG(
Filter(
Descendants([Issue].CurrentMember, [Issue].[Issue]),
DateInPeriod(
(
[Measures].[Transition to status last date],
[Transition Status].[Ready to deploy],
[Time].CurrentHierarchy.DefaultMember
),
[Time].CurrentHierarchyMember
)
),
DateDiffWorkDays(
(
[Measures].[Transition from status first date],
[Transition Status].[Prioritized],
[Time].CurrentHierarchy.DefaultMember
),
(
[Measures].[Transition to status last date],
[Transition Status].[Ready to deploy],
[Time].CurrentHierarchy.DefaultMember
)
)
)
Make sure that you set Formatting to Numeric field for this measure.
2)Report Average time in status (Cycle time) - Issues - Jira Demo - eazyBI has been filtered to only show Statuses in “To Do” and “In Progress” category. You can change it to include all transition statuses & it will return the average time in each Transition status.
Great, thank you for the response @Marita_Norvele . Using the formula suggested by you in 1st point, i am able to see value for some of the team but for some team, i am getting blank value. Can you confirm what could be the possible reason behind it?
Is it possible that the filtering with time is impacting this? I mean what if i choose January 2025 in the time? Will it exclude those records which were set to “Priortized” in December 2024 ?
The selected member in the Time dimension applies to issues that have transitioned into the Ready to Deploy status. So, if you select January 2025 in the Page filter, you will only see issues that transitioned into Ready to Deploy during this period. This ensures that only relevant issues are considered based on the selected time range.
In the second part of the formula, DateDiffWorkDays uses the Default member of the Time dimension. This means that after verifying that an issue has reached the Ready to Deploy transition status, the formula ignores the selected time period and instead calculates the average transition time regardless of what is chosen in the Time filter.
My first assumption is that you do not see results for a specific team because they did not have any issues transitioning into the Ready to Deploy status during the selected time period.
However, if that is not the case, we will need to investigate further. The best approach would be for you to identify an issue that was assigned to this specific team and transitioned to the Ready to Deploy status within the selected time period. Please send the JSON details of this issue to our support email at support@eazybi.com, and we will look into it.
@Marita_Norvele Is it possible that the date in Page filter shows the records on the basis of “Priortized” status? E.g., if we choose January 2025, then it should show only those records that were set to priortized in January month and was able to make it to ready to deploy status.
