Report based on inherited attribute across hierarchy

Questions & Answers
,
2

In eazyBI, you can import an issue linked field dimensions for issues in Sub-task, Epic, and Portfolio hierarchies. This option works for standard dimensions, like Label, Priority, Fix version, and other: Issue link field dimensions.

You can also create a similar dimension on another issue field from the Portfolio hierarchy as long as it is a single-select custom field. In that case, you may define a new JavaScript calculated custom field that would return custom field value and pass it down to child issues.
The structure for JavaScript calculated custom field “Demand Bundle” might look like this, where NNNNN is custom field “Bundle” ID in Jira:

[jira.customfield_NNNNN_jpoh3]
name = "Demand Bundle"
data_type = "string"
dimension = true
update_from_issue_key = "jpoh_parent_3"
javascript_code = '''
if(issue.fields.customfield_NNNNN ) {
   issue.fields.customfield_NNNNN_jpoh3 = issue.fields.customfield_NNNNN;
}
'''

Before applying this code, please see how to test the JavaScript beforehand and how to create a JavaScitp calculated custom fields: JavaScript calculated custom fields.

Please see the documentation on JavaScitp calculated custom fields and how to test them beforehand: JavaScript calculated custom fields

The given code has parameter update_from_issue_key = “jpoh_parent_3” that describes from which Portfolio hierarchy level eazyBI should get the custom field value. In your case, the issue keys would be like this:

  • Demand, jpoh_parent_3
    • Epic, jpoh_parent_2
      • User Story, jpoh_parent_1
        • Sub-Task

Check out also this Community post on how to assert the right issue key for each Portfolio hierarchy level and import linked field dimension:

Best,
Zane / support@eazyBI.com