Epic level custom field

eazyBI for Jira

eazyBI analyzes data based on values on issues. However, in some cases, values in some fields are added for epics, parent issues, or other higher-level issues in a custom hierarchy. The reports will not give values from issues in Epic, sub-tasks, or any lower-level issue when the dimension is used for filtering data. Issues should inherit these values during import. eazyBI supports issue link field dimensions for some default fields (Fix Version, Label, Status, Resolution, Issue type, Priority). 

For other single-value fields, you can define inherited fields with calculated JavaScript custom fields or new calculated fields. This option is not supported for multiple-value fields.

Define a new calculated JavaScript custom field. Use a formula to assign a value of the field you would like to inherit to this newly created custom field. Then, you use the parameter update_from_issue_key  to specify from what hierarchy level you would like to pass down the values.

The example below will pass down values from the Epic issue custom field to issues in epics. Please use the custom field ID instead of NNNNN  in any place in the examples below. You can set the desired name instead of the "Epic custom field name".

Account-specific calculated field

Account specific calculated fields are defined in Source Data → Import options.

Settings for the new field

update_from_issue_key = "epic_key"

Custom JavaScript code:

for Jira single-line text fields

//for single line text field
if(issue.fields.customfield_NNNNN ) {
   return issue.fields.customfield_NNNNN;
} 

for Jira Select option (single-choice) fields

//for select list single choice
if(issue.fields.customfield_NNNNN) {
   return issue.fields.customfield_NNNNN.value;
}

For Jira single user picker fields.

//for single user picker fields
if(issue.fields.customfield_NNNNN ) {
   return issue.fields.customfield_NNNNN.displayName;
}

Global calculated field

Global calculated fields are defined in eazyBI advanced settings.

Here are the settings for the new field definitions. You should insert the JavaScript (the code given above) below the line // Insert here the Custom JavaScript code. Keep the opening and closing quotation marks. ''', do not delete them.

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

Here are the parameter options for other Issue dimension hierarchies:

• update_from_issue_key = "epic_key" if you would like to pass down values from the Epic to the issues within it;
• update_from_issue_key = "parent_issue_key" if you would like to pass down values from the parent issues to the sub-tasks;
• update_from_issue_key = "jpoh_parent_X" if you are using the Advanced Roadmaps hierarchy and would like to pass down values in this hierarchy. Use a parent level number 1,2,3,.. instead of X counting parent levels on top of sub_tasks. 1 for story level (jpoh_parent_1), 2 for epic level (jpoh_parent_2), 3 ...;
• If you are using a custom Issue hierarchy, you can address the custom fields used for levels to pass down values in the custom hierarchy. For example, update_from_issue_key = "customfield_feature" for the Hierarchy with epics and Features to pass down values from feature issues.