Resolved but not closed - creating new measure

Questions & Answers
1

Hi,
I’m fairly new to EazyBI and so far I’ve managed with simple measures and updating the work of my predecessor. Now I ran into a problem I can’t figure out myself.

Our development teams often resolve bugs but forget to close them. So I’d like to create a new measure which finds bugs that are resolved but not closed. How do I do that?

Thanks in advance. :slight_smile:

2

Hi @jps,

Welcome to the eazyBI community. I am sorry your question didn’t get any attention sooner.

In eazyBI, issues with resolution dates are considered resolved. So, as the first building block, you can use the measure “Issues resolved”:

[Measures].[Issues resolved]

Next, as you want to consider a specific issue type, let us add the Issue Type dimension and form a tuple:

(
  [Measures].[Issues resolved],
  [Issue Type].[Bug]
)

That will give you all the resolved bugs. Now, you can explore several options to determine the resolved but not closed bugs. I recommend subtraction - subtracting the number of closed resolved bugs from the resolved ones. For that, you need to determine the status that marks the issue closed. If it is only a single status, you can use a formula similar to the one below:

(
  [Measures].[Issues resolved],
  [Issue Type].[Bug]
)
-
(
  [Measures].[Issues resolved],
  [Issue Type].[Bug],
  [Status].[Closed]
)

Please see the eazyBI documentation page for more information on defining calculated measures -​ Calculated measures and members.

Best,
Roberts // support@eazybi.com