Issue Hierarchy: Feature --> Epic --> Story, when using "Parent" and not specific link - how to configure?

We have an hierarchy of Feature → Epic → Story

We used link (In Feature) and it all worked ok with the below definition:

[jira.customfield_feature4]
name = "Feature4"
outward_link = "In Feature"
issue_type = "Feature"
update_from_issue_key = "epic_key"

[[jira.issue_hierarchies]]
name = "Feature Hierarchies4"
all_member_name = "All Issues by Feature Hierarchies4"
levels = [
  {name="Feature",key_column="customfield_feature4",issue_type="Feature"},
  {name="Epic",key_column="epic_key"},
  {name="story",key_column="epic_parent_key"}
]

Then, we started to use “Parent” hierarchy, also from the “Feature” to “Epic” (see picture), and I can’t find the correct definition.
I check the relevant pages, but didn’t find the answer.
Issue Hirrarchy

How should I configure it?

Thanks

@Omer_Sela

check how to define Issue.Parent hierarchy in eazyBI for Jira CLoud:
https://docs.eazybi.com/eazybi/data-import/data-from-jira/plans-custom-fields#Planscustomfields-JiraCloud

Martins / eazyBI

1 Like

Perfect!! Many thanks