Hi !
I’m new at EasiBI and I’m having a hard time producing a dashboard that would show the number of days spent on the US that could be easily compared to it’s originel story points.
This team is having trouble identifying the right story points to give at the begining so it would be interesting to identify over a periode of two months for exemple which US took a lot of time while it should have been an easy one.
The dashboard would allow the team to track their progress concerning its capability to estimate and take action during review or retrospective.
Thank you so much for your help <3
Thibault
PS : sorry for my bad english, it isn’t my first language.
Hi @Thibault,
Welcome to the eazyBI community! Don’t worry about your English; it is all right 
.
How do you determine the duration it took for the issues to be completed? Out of the box, I can think of three options. The first is the duration it took to resolve the issue. eazyBI has a predefined measure, “Average resolution days”, which will return the average number of days from the issue creation till resolution. With the Issue dimension “Issue” level members in the report rows, this measure will return the duration it took to resolve each issue. Jira Core measures and dimensions.
Another option is the “Issue cycle” functionality, where you can define specific cycle statuses to consider for the duration. eazyBI will then create predefined measures, one of which is the duration issues spent in those particular statuses. I recommend using the “ days of resolved issues” measure. Issue cycles.
The third option could be viable for the duration in a single status - defining a tuple in a calculated measure with the Transition Status dimension member of the status and the measure “Days in transition status”. Calculated measures.
Please see a screenshot with the first two options for a particular project Stories resolved in January 2022:
Best,
Roberts // support@eazybi.com
