Measure number of bugs caused by assignee

I am trying to create a report where I’d display

  • Number of Completed Tasks
  • Number of Approved Tasks
  • Number of Rejected Tasks
  • Number of Tasks casing Bugs

Report should be something like this

First four measures are simple as I can add Reviewer as Rows, Time as Page, and Completed, Accepted, Failed as Measures since I have this imported.
However, last one “Regressions” is giving me some trouble because I want to measure how many tickets done by the Assignee caused N number of Bugs.
In JIRA I have the link set as ‘Causes’ and ‘Caused by’ and in EazyBI I added custom JS code for calculated measure as follows

name = "Regressions"
outward_link = "caused by"
multiple_values = true
measure = true
dimension = true

The problem is that it looks into Tasks done by assignee and checks how many Regressions it has which is not correct. A bug ticket might be done by Assignee 1 while ticket causing the Bug is done by Assignee 2 and I’d like to show this in Report under Assignee 2.

Can anyone help with the proper approach to this?

Hi @Milos_Sretin

Welcome to the eazyBI community!
Great that you have already imported issue links, we will use property with linked issues in the calculation.

To count tasks that caused some bugs, you may want to create a measure (in Measures) that iterates through all tasks, assigned to the assignee in rows, and count those having some value in the “Issue Regressions” property.

    Descendants([Issue].CurrentMember, [Issue].[Issue]),
      [Measures].[Issue creation date],
     Not IsEmpty([Measures].[Issue Regressions])
     -- filter by type if it is necessery
     [Measures].[Issue type] = "Task"
-- count issues in the report context - selected Time, Assignee etc
     [Measures].[Issues created]

Please check the correct property name for [Measures].[Issue Regressions].
If you do not need to filter by issue type, remove the condition.

Ilze /

I am not looking to count only those that have regressions.
In fact, I want to count several regressions.

For example:
There might be 2 tickets, where 1st has 1 regression, and 2nd has 5 regressions.
This shouldn’t show in the report as 2 (having regression) - it should show as 6.