All bugs without labels

Hey there,
I am trying to do a report on all bugs that don’t have a set of labels. So I added a member to Label, named X:


And try adding multiple ways to Issue (Named Y), that last attempt was something like:

  ([Measures].[Issues created], 
  [Issue Type].[Bug], 
  [Label].[X]) > 0

The rows I have are Issue.Y and Time (by month). The measure I added for now is Issues Created. I get a 60 second timeout when running this.

This seems like a simple requirement. How many bugs are created over time without a set of labels.

Please help

@lauma.cirule @zane.baranovska @gerda.zandersone @martins.vanags @ilze.leite Can anyone of you answer this please?

Hi @Uris,

I believe you already have sorted out this use case with eazyBI Support.

A label is a multi-selection field, and therefor filtering issues without some labels are tricky. As issue may have one valid label and one you would like to exclude.
Your idea to create a calculated measure that validates labels of all issues is correct. Unfortunately, this type of calculation is quite heavy and resourceful, but there are some improvements you can make.

  1. In the Label dimension, create a calculated member that aggregates all labels you would like to exclude for bugs. I will refer to this calculated member as “Labels ABC”.

  2. Then you may write the calculated measure in Measures to count defects without labels A, B, or C like this:

        --go through the set of issues with type Bug
        Descendants([Issue].CurrentMember, [Issue].[Issue]),
        [Measures].[Issue type] = "Bug" AND
        --do not have any of labels A, B or C
          ([Label].[Labels ABC],
          [Measures].[Issues created count]) )
      [Measures].[Issues created count]

    In this formula is used measure “Issues created count” that shows a count of created bugs without labels A, B or C. You may use measure “Issues resolved count” instead if you would like to count resolved bugs without labels A, B or C.

  3. In the report, use the new calculated measure (from the point 2.) on columns. On rows set dimension how you would like to group data, for example, by Project, Priority, or other.

Labels are quite handy in Jira because this is a multi-selection field, and users can put in a different type of information and business logic. In the reporting is turns out to be challenging for one viewpoint (Label dimension) to represent many types of data (hidden business logic). An alternative solution is to create new dimensions during data import into eazyBI to represent each type of information in a separate dimension based on Lable value combinations. To create those new dimensions, you may use JavaScript calculated custom fields:

Zane /