First let me say eazyBI has been a godsend for use for detailed reporting. We're getting a lot of useful data from the reports I've created in only the first week of use.
Currently I am tasked with generating an open issue aging report that can be drilled into from our overall division, to each team (which is from JIRA groups I am importing, and then to the individual employees. Step 1, creating an overall group, was an easy calculated member:
However, while this gives me a nice breakdown I quickly realized that there are several employees that are members of more than one group. This ends up skewing the numbers at overall and team levels, since these people have their open issue counts listed multiple times.
My thought was I could create groups as calculated members, then change the calculated member aggregate listed above to use these calculated members instead of the jira groups. Each calculated member would be an aggregate of all members of a specific group, minus the duplicated member. My problem is that I cannot figure out the proper calculation to do this.
For reference points, let's say my JIRA groups contain the following members.
jiraGrpA = emp1, emp2, emp3
jiraGrpB = emp1, emp4, emp5
jiraGrpC = emp1, emp4, emp6, emp7
Unfortunately, the idea with calculated members instead of the groups has a shortage. The reason is that calculated members are independent and they can not see other member and adjust the calculation depending on the other member calculation. So, in your example, emp1 is a duplicate for all the groups, and you need to tell eazyBI for which group it should be excluded. If you wish to count a user for exactly one group, you will end up managing an alternative user/group configuration in eazyBI with the formulas like this:
-- set of users filtered by group
-- set of users to be excluded
EazyBI considers it as the correct approach when the measure adds the fact for each of the dimension members when there are multiple members of a dimension to which the fact is related. Workarounds for such cases are when you can tell the algorithm how eazyBI can decide which group is "the right" from group names or some other group attribute.
Introduction This article will give insight on how a small software development department implemented Atlassian products to enhance and streamline the business process. The privately held company h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs