Issue link field dimensions
eazyBI for Jira
This page describes advanced JIRA and eazyBI integration. If you need help with this please contact eazyBI support.
Jira Software, Advanced Roadmaps, issue linking provides an option to build issue hierarchies in Jira and import new hierarchies into eazybi. Different fields could be managed on different hierarchy levels. This section describes an option to analyze data of lower levels, for example, time tracking, story points on stories, sub-tasks by fields on higher levels issues, for example, Epic Fix version. The same option could be used for single linked issue field analysis.
eazyBI supports building new dimensions for some Jira default fields (Fix Version, Label, Status, Resolution, Issue Type, Priority) of linked issues, for example, Epic Fix version, Feature Label, etc.
If you would like to import a linked field dimension into eazyBI, you need to add the definition of this linked field dimension to advanced settings for custom fields.
At first, you need to give a name for dimension using the field ID
issue_link_field_dimensions, for example:
Then specify which Jira default field should be used, for example:
Now, you should set the reference to the linked issue custom field
You can use KEY columns describing the hierarchy level or one linked issue.
For example, if you have a custom field_feature with one linked Feature issue, you can use a reference to it:
Here are options for
issue_key_column values using other default hierarchies:
issue_key_column = "subtask_parent_key"if you would like to get values from parent issues to sub-tasks
issue_key_column = "epic_key"if you would like to get values from linked epic to its child issues and sub-tasks
issue_key_column = "jpoh_parent_X"if you are using the Advanced roadmaps hierarchy and would like to get 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/standard issue level (jpoh_parent_1), 2 for epic level (jpoh_parent_2), 3 ...
then you can set a group in dimension selection:
Linked dimensions import and usage
After you have saved the advanced settings with the linked field dimension definition, then go to the Source Data tab and see if you have this dimension in the list of available linked dimensions in Additional options tab.
Select the dimensions you need for data analysis for import in each account.
eazyBI builds link field dimensions with the same structure as default dimensions. They will have the same hierarchies and member structure as default dimensions. eazyBI supports access to the same set of properties as default ones as well.
The example formula above retrieves the release start date for Epic Fix version dimension members.
Epic Fix version
The example above describes how to analyze stories and sub-tasks based on the Epic Fix version.
source_dimension in this case, is Fix Version, and you can use the field epic_key in
The example above describes how to analyze stories and sub-tasks based on Epic Status. In this case,
source_dimension is Status dimension, and you can use the epic_key in
issue_key_column. This definition is similar to the Epic Fix version, but the Status dimension is used instead of the Fix Version.
The example above describes how to analyze stories and sub-tasks based on Epic Label. In this case,
source_dimension is Label dimension, and you can use the epic_key in
issue_key_column. This definition is similar to the Epic Fix version and Epic Status examples above.
The example above describes how to analyze sub-tasks based on parent issue's status. In this case,
source_dimension is a Status dimension, and you can use the field subtask_parent_key in
issue_key_column. This definition is similar to the Epic Status, but this time the value is copied not from the epic, but from the parent issue of a sub-task
Parent Fix version
Similar to how stories are analyzed based on the Epic Fix version, it can be done based on the Parent Fix version. In this case, use
This example would work for Advanced Roadmaps hierarchy. Here we assume that Initiative is one level above Epic in the hierarchy.
See the chapter on the configuration above on how to use the right issue_key_column configuration here for Advanced Roadmaps hierarchy levels that you want to copy status values from to all levels below. The levels for Advanced Roadmaps hierarchy are counted starting from the bottom; for example, the first level above Sub-tasks has value jpoh_parent_1.
If you have a linked Feature grouping your Epics, you can define it with Issue link import and then create a new dimension Feature Label enabling data analysis by Feature Labels in Epics, Stories, Sub-tasks:
The first definition describes the issue link Feature. Then you can use the Feature custom field in
issue_key_column as a reference and specify the field Label as