Parent Epic Link dimension

[Christophe]

Hi,

Is it possible to create a Parent Epic Link dimension in the advanced settings (same principle as Parent Fix Version or Parent Issue Type)?

I’ve tried with the syntax below and it doesn’t work :

[[jira.issue_link_field_dimensions]]
name = “Parent Epic Link”
source_dimension = “Epic Link”
issue_id_column = “subtask_parent_id”
group = “Linked issue dimensions”

Thanks.

Regards,
Christophe

[daina.tupule]

Issue link field dimension feature is in high demand. However, it applies to some Jira default fields only ( Fix Version, Label, Status, Resolution, Issue type, Priority ). We update a list of supported fields on our documentation as well.

Here are other options on how you can achieve the same with other options. It is limited to any Single value dimensions and values only, though.

You can use update_from_issue_key as an additional parameter for any field to pass down values to other issues. We suggest creating a new calculated JavaScript custom field to retrieve any single value custom field value and add the parameter update_from_issue_key and use an applicable custom field referencing to issue key to pass down the values (similarly like Issue link field).

Here is one community post you can check as an example:

Aggregate story points on stories under a epics grouped by a custom attribute

This worked beautifully. One weird thing though: after I clicked the “import” button, the data was there–then the next day it was all gone! I had to uncheck the boxes in the import settings, re-run the import; then RE-CHECK those boxes in the import and rerun the import. Then the data re-appeared. This is very mysterious. Known issue?

On Jira cloud, this is the only way how to access Epic Link value. There might be a slight modification for the same formula (Epic link has a bit different data structure in Issue JSON than single select custom field):

[jira.customfield_parent_epic]
name = "Parent Epic Link"
dimension = true
data_type = "string"
update_from_issue_key = "parent_issue_key"
javascript_code='''
if (issue.fields.customfield_NNNNN) {
  issue.fields.customfield_parent_epic=issue.fields.customfield_NNNNN;
}
'''

You would like to use Epic Link custom field ID instead of NNNNN. I used parent_issue_key as a parameter to pass down value from parent issues to sub-tasks.

On Jira server, I would suggest using a different option. We have an additional option to access Epic Link via issue links in Jira server. Issue link field import gives additional options to see the dimension similarly like issue dimension.

[jira.customfield_parent_epic]
name = "Parent Epic"
inward_link = "has Epic"
issue_type = "Epic"
dimension = true
update_from_issue_key = "parent_issue_key"

Daina / support@eazybi.com