Custom issue hierarchy

Questions & Answers
,
1

Hi Everyone,

I’m trying to setup custom issue hierarchy in eazybi

Initiative/Project → Epic → KR/Component → Story → Task

(Issue link → Epic Link → Issue Link → Issue Link)

I have used below configuration in eazybi settings, however I get hierarchy from Epic to Task only, Initiative is not included in the hierarchy even though link is valid and exists between issues

Any thoughts would be helpful

below is the configuration

*[jira.customfield_initiative]
name = “Initiative”
inward_link = “Epic to Initiative”
issue_type = “Initiative/Project”
dimension = true
update_from_issue_key = “customfield_epice”

[jira.customfield_epice]
name = “E Epic”
inward_link = “has Epic”
issue_type = “Epic”
dimension = true
update_from_issue_key = “customfield_kr”

[jira.customfield_kr]
name = “KR Component”
inward_link = “Story to KR Component”
issue_type = “KR/Component”
dimension = true
update_from_issue_key = “customfield_story”

[jira.customfield_story]
name = “Story”
inward_link = “Tasks to Story”
issue_type = “Story”
dimension = true
update_from_issue_key = “parent_issue_key”

[[jira.issue_hierarchies]]

name = “Initiative”
all_member_name = “All Issues by Initiative”
levels = [
{name=“Initiative”, issue_type = “Initiative/Project”, key_column=“customfield_initiative”},
{name = “Epic”, key_column=“customfield_epice”, issue_type=“Epic”},
{name=“KR/Component”,key_column=“customfield_kr”, issue_type=“KR/Component”},
{name=“Story”,key_column=“customfield_story”,issue_type=“Story”},
{name=“Task”, issue_type=“Task”, key_column=“subtask_parent_key”}
]*

2

Hi, Leo,

Welcome to the eazyBI community!

Thank you for sharing your configuration!

Looking at your setup, there are a couple of things to check to get the Initiative level working:

1. Verify the issue link name and direction

The inward_link value must exactly match the link name as defined in Jira, and the direction matters. To confirm the correct link name and direction between your Epic and Initiative issues, open an Epic in Jira and replace browse with rest/api/latest/issue in the URL to get its JSON. Look for the issuelinks section to see the exact link type name and whether it is inwardIssue or outwardIssue from the Epic’s perspective.

2. Check the update_from_issue_key chain

The update_from_issue_key propagates values downward from parent to child levels. Your chain looks like:

  • customfield_initiative → update_from_issue_key = "customfield_epice" (Initiative value passed to Epics ✓)

  • customfield_epice → update_from_issue_key = "customfield_kr" (Epic value passed to KR/Component ✓)

  • customfield_kr → update_from_issue_key = "customfield_story" (KR value passed to Story ✓)

  • customfield_story → update_from_issue_key = "parent_issue_key" (Story value passed to sub-tasks ✓)

This chain looks correct in principle, but it will only work if customfield_initiative is actually being populated for Epics after import. If the link name or direction is wrong, the Initiative field will be empty and won’t show in the hierarchy.

Kindly,
Ilze

3

Hi Ilze,

thanks for the response, I have responded the support request I have raised

Regards,

Leo