Import issue links
eazyBI for Jira
This page describes advanced JIRA and eazyBI integration. If you need help with this please contact eazyBI support.
If you would like to import selected issue links into eazyBI you need to define additional calculated custom fields using advanced settings for custom fields.
At first, you need to give a name for this issue link calculated custom field:
- Use your own
customfield_NAMEcustom field name where
NAMEis some unique descriptive name of your additional calculated custom field. Best practices for naming the custom fields: keep it short, without underscores, special symbols, or camelCase.
- And a
namesetting and specify a display name for this calculated custom field that will be visible in Jira import custom fields selection (these calculated custom fields will be always visible for any Jira project selection).
Then specify if it will be an
inward_link from an issue and specify the name of this link, for example:
You can specify also several outward or inward links, for example:
If issues with different types can be linked using the specified links then optionally you can also limit that only issues with specific issue type will be selected:
or several issue types:
If you would like to update this calculated issue link field for sub-tasks from their parent issues then specify
update_from_issue_key. This parameter should reference to some default fields or custom fields containing single issue key:
If you would like to import this custom field as a dimension (that means not just as a property) then add
If there can be several linked issues with the specified link type and you would like to import them as a multi-value dimension, then specify:
update_from_issue_key does not work with
multiple_values = true
After you have saved the advanced settings with this issue link field definition then go to the Source Data tab and see if you have this custom field in the list of available custom fields.
Features and Themes
This is an example where issues are grouped into features (by linking issues to features) and then features are grouped into themes (by linking features to themes):
In this example, all issues (with their subtasks) within features will also be related to the corresponding theme. At first,
customfield_feature will be updated for sub-tasks using the
parent_issue_key field (which stores the parent issue key for sub-tasks). And then
customfield_theme will be updated for parent issues and sub-tasks using the
If you have many bugs that can be related to one story or feature and you would like to see by bug which issues it is related to then you can import them as a multi-value dimension:
There might be cases when issue link configuration parameters seems not working as expected. Here follow hints which might help faster find out the reasons why issue link information is not imported in eazyBI correctly.
- Check if you have correctly used inward_link or outward_link direction of the link.
The general rule: check the link name in the issue screen you consider as a "parent" issue (for instance, if you want to get all defects logged against a task, then check the link name in the task issue screen). Then go to Jira administration and check whether this name is for inward on outward endpoint of the link. Keep in mind that link name could differ accordingly to its direction!
- You need to use the correct name (all spaces, upper/lower case) of the inward or outward link configured in Jira. To avoid misspellings, it is a good idea to copy the name from the Jira configuration screen. It is even a better idea to copy the link name from the edit screen since it will show some possible leading or trailing spaces which might accidentally be entered in the link name:
You also can check the specific issue to see if the issue link is used as intended by the configuration.
For the example above, following settings should be used to create a correct custom field for the hierarchy (mind the space in inward link name!):
- Whenever you change the advanced settings for a custom field or hierarchy it is recommended to either do the full reimport of the data in the account, or to clear the previously loaded custom field configuration (run the import with the custom field un-checked) and load it again (run the import with the custom field checked).