Hi, I need help creating a new user defined calculated measure that will sum another user defined calculated measure (QA Factor) for each subtask assignee per release. For example, I have 5 issues where 3 of which have subtasks assigned to me and each of those issues have received a QA Factor (5,4,3,etc). I need a sum of the QA factors for only those 3 issues. I was hoping my report will look like below displaying that sum (QA Capacity) for each assignee.
Hi @Alyssa_A
I see you filter the report by “Status” and you use “Target_Release” dimension in rows.
How should these fields filter sub-tasks?
You mentioned that you want to count sub-tasks for the assignee. But then how should the “Status” filter them?
Is that the status of the sub-task itself or status of a parent for the subtask?
The same question about Target_Release field - is it used on sub-task or it’s parent?
Also, what is the custom field type for the field “QA Factor” in Jira (number, free text, select list etc).?
And what is the current “QA Capacity” formula in your report?
Martins / eazyBI
Status and Target_Release are from the parent tasks. I think I need to remove that parent task status filter actually. I’ll want to count the QA factor unless the specific “System Testing” sub-task is in a closed status with a resolution of “Won’t Do”. And I don’t know if it will be important to know but there are usually two “System Testing” sub-tasks assigned to my team, when either of those “system testing” sub-tasks are assigned I need to sum the QA factor.
The QA Factor is a number based on the parent tasks QA LOE. I currently have this for QA Capacity but I know I’m way off…
Sum(
Filter(
Descendants([Issue].CurrentMember,[Issue].[Issue]),
Not IsEmpty([Issue].CurrentHierarchyMember.Get(‘QA Factor’))
),
CASE WHEN [Measures].[Issues created] > 0
THEN
[Measures].[QA Factor]
END
)
What is the custom field type for both QA LOE and Target_Release fields ?
And do I understand you correctly - QA Factor is not a Jira field?
Also, you mentioned two “System Testing” sub-tasks.
Which field do you use in Jira for a sub-task to mark it as “System Testing”?
Martins
Sorry about that. They are both Single-select fields. Correct, QA Factor is not a JIRA field, it is a user defined calculated measure. And it is the Subtask Type field that defines “System Testing”.
The idea is to import new calculated field “Parent Target_Release” and “Parent status” which both inherit values from the parent and copies them to sub-tasks and then filter report by parent field values to calculate sub-tasks.
Please find the documentation page where we described how to define and import such fields in eazyBI:
https://docs.eazybi.com/eazybi/data-import/data-from-jira/javascript-calculated-custom-fields/calculated-field-examples/epic-level-custom-field
In your case, the Javascript code should be something like this where you use the 5digit custom field ID from Jira for Target_Release instead of NNNNN
//for select list single choice
if(issue.fields.customfield_NNNNN) {
return issue.fields.customfield_NNNNN.value;
}
In the additional advanced settings, use this code:
update_from_issue_key = "parent_issue_key"
Here, it is explained how to import the “Parent status” dimension to let you filter the report by the statuses of the parent issue—because you want to count sub-tasks by their parent status.
https://docs.eazybi.com/eazybi/data-import/data-from-jira/advanced-data-import-options/issue-link-field-dimensions#Issuelinkfielddimensions-ParentStatus
When both fields are imported as dimensions from the import options page, in report layout use “Parent Target_Release” in rows and “Parent Status” as page filter instead of regular Target_Release and Status dimensions.
Next, make sure you have defined your “closed” status for issues closed measure in the import options page. That will count closed sub-tasks with particular “closed” status.
Also, make sure that custom field “QA LOE” is imported as a dimension from import options page.
Finally, create a new calculated measure using this formula:
(
[Issue Type].[System Testing],
[Measures].[Issues closed],
[Resolution].[Won't Do],
[QA LOE].[Very High]
)*4
+
(
[Issue Type].[System Testing],
[Measures].[Issues closed],
[Resolution].[Won't Do],
[QA LOE].[High]
)*3
+
(
[Issue Type].[System Testing],
[Measures].[Issues closed],
[Resolution].[Won't Do],
[QA LOE].[Medium]
)*2
+
(
[Issue Type].[System Testing],
[Measures].[Issues closed],
[Resolution].[Won't Do],
[QA LOE].[Simple]
)*1
That should do the trick.
Martins / eazyBI