I work for a company using EazyBI for Jira product with a 10k user base, having moved our full marketing production tracking in to JIRA over 12months ago now, based on some reasonably complicated workflows. We’re now looking to EasyBI to help us move from basic reporting to produce much more detailed insights based on the rich data we now have.
Our workflow statuses look something like: DRAFT, JOB OPEN, SUBMIT OUTLINE, OUTLINE REVIEW, SUBMIT BRIEF, BRIEF REVIEW, IN PRODUCTION, LIVE.
We’re trying to build a calculated measure which tells us how long it took for the job to get from JOB OPEN status to LIVE status, and I was hoping someone could tell me if it’s possible to build a query to look at that?
Thanks in advance
You can measure cycle time in particular statuses using
historical measures with dimension Transition Status. Those measures represent data from issue change history. There are a list and description of those metrics and how those work:
We have created several templates fo Cycle time reports and solutions you might want to start with.
Report templates are available in the Demo account. You might want to start with those:
And several solutions are described in listed
Community posts as well:
eazyBI has some “out of the box” measures, like Average resolution days, Days in transition status, Closed issues, Transitions from status, etc. However, each business case is slightly different and therefore KPIs for each business case are calculated differently as well.
It is very likely that you will define
new calculated measures to reflect process flow for your business case.
For example, to calculate cycle time, you can build a report based on issue change history. You may use dimension T…
Here is one report example in our demo account on
cycle times. This report works on historical status change and will count total time in any status from status category In Progress (Transition status hierarchy by Category In Progress).
The measure Rolling Average cycle time also includes an alternative solution, to an average time spent within a specified list of statuses.
However, if this report example, does not suit you. You can define a new calculation based on the time when an issue move…
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…
Zane / support@eazyBI.com