Unable to create Issue Link Field Dimension for eazyBI Report

[Gaurav]

Hello All,

We need to create a report where the filter would be on the Quarter field of the Epic and need to add the efforts for issues under the epic. The custom field 'Quarter' is available only at the Epic level. 

The report needs to be filtered based on the custom field 'Quarter'. If we filter based on Quarter, it filters out all the underlying issues (stories, tasks, sub-tasks) as they do not have the custom field. 

Based on the documentation, this can be achieved using the Issues Epic Hierarchy. We added the code in Advanced Settings for 'Issue Link Field Dimension' and performed a full import but it did not create the Link Field Dimensions. The code added to Advanced Settings was the same as provided in the documentation: https://docs.eazybi.com/eazybi/learn-more/learn-eazybi-through-examples/issue-hierarchies#Issuehierarchies-IssueEpichierarchy

Kindly suggest the optimal solution to filter data based only on the quarter field of Epic ensuring that the underlying issues (stories, tasks, sub-tasks)  are not filtered.

[Nauris Malitis -eazyBI-]

Hi Gaurav,

If your "Quarter" field is a single value field in Jira attributed only to Epics, and you would like to filter Epic child members by this Epic value, you can introduce an Inherited field dimension in Advanced settings with the help of custom Javascript code:

[jira.customfield_NNNNN_e]
name = "Epic custom field name" 
data_type = "string"
dimension = true
update_from_issue_key = "epic_key"
javascript_code = '''
if(issue.fields.customfield_NNNNN ) {
issue.fields.customfield_NNNNN_e = issue.fields.customfield_NNNNN;
}
'''

Replace the NNNNNs with the IDs of your custom field. The "update_from_issue_key" parameter will specify from which hierarchy level you would like to pass down the values.

When this is saved, go to your Jira import options, select this new field for import, and you should see the "Epic custom field name" dimension available in your report creation section.

Best regards,

Nauris / eazyBI support