nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

EazyBI - Time in each status

James Weaver

I'm new to EazyBi but trying to create a measure that will show how long each issue has spent in each status. i.e if an issue took 40 days from opening to close how do I show it spent 10 days in validation - 10 days in mitigation - 10 days in implementation etc.

Can this be done in EazyBI.

Thanks

Accepted answers

Gary Pasquale

Hi @James Weaver,

Yes, eazyBI can be used for that.

And it's relatively simple to set up. We use it for exactly that measurement.

Regards,

Gary

All comments

Gary Pasquale

Hi @James Weaver,

Yes, eazyBI can be used for that.

And it's relatively simple to set up. We use it for exactly that measurement.

Regards,

Gary

James Weaver

Do you have a demo or an example you can share?

Gary Pasquale

@James Weaver - I have a word doc with some notes I made a while back. But can't attach here. If you share an email address I can forward it to you.

James Weaver

Thank you - james-simon-weaver2@hotmail.com

Martins Vanags_eazyBI

Hi James,

It would be possible to use eazyBI and calculate the time issue spent in a specific status (or even calculate the average result on the project level) by importing issue change history.

Then you could use "Transition Status" dimension and measure "Days in transition status"

You could read more about the transition-related calculations here: https://docs.eazybi.com/display/EAZYBIJIRA/Import+issue+change+history

Please also check two eazyBI sample reports:

https://eazybi.com/accounts/1000/cubes/Issues/reports/145950-average-days-in-transition-status

and

https://eazybi.com/accounts/1000/cubes/Issues/reports/61947-days-in-backlog

Martins / eazyBI team

Steve McGee

Good stuff.

"Average" is not as valuable as being able to get the actual, specific days in each status for each issue (and more importantly, for each type of work).

Because when you are able to capture this - which we can do without software - you can

generate highly predictable forecasts
set reasonable expectations with customers and have everyone be happy
manage dependencies easily
allocate capacity effectively
significantly reduce (eliminate) risk of missing a due date
better define policies so staff can make decisions without waiting for managers
spend WAY less time estimating, and interrupting expensive people to estimate

etc.

Karthiga Sethuraj

@Martins Vanags_eazyBI

I tried to create a bar chart using the instructions provided by you in this thread to get the Average time spent by a set of resolved issues in each status for a given time period.

In Rows, I selected the below dimensions:

- Transition status ("All Transition Statuses" member)

- Issue

- Time

In Columns, I selected the below Measures:

- Issues Resolved

- Average workdays in transition status

I am able to get data when I filter by Month in Time dimension but get an empty table when I filter by Weekly Members or a custom hierarchy to get data biweekly.

Could you help debug this issue please ?

Thank you for your help !

Martins Vanags_eazyBI

@Karthiga Sethuraj

Our sample reports on the demo account usually work for all default hierarchies from "Time" dimension?

But could you please share more details about your custom hierarchy for biweekly data?

There is no such hierarchy in the "Time" dimension as far as I know.

Martins

report with weekly hierarchy.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira