Sub-tasks not Shown in Custom Hierarchy

Questions & Answers
1

Hi there,

I’m trying to build a custom hierarchy in EazyBI Server (not cloud).

It works for Epic → Story → Task. Unfortunately, Sub-tasks are not showing at all under their parents Tasks.

Hierarchy:

  1. Epic → Story - standard Jira Epic Link field
  2. Story → Task - custom Issue Link type called “Parent-Child”, outward description “is parent of”, inward description “is child of”
  3. Task → Sub-task - standard native Jira sub-task parent relationship

My current configuration:

[jira.customfield_story_link]
name = “Story (via link)”
outward_link = “is parent of”
issue_type = “Task”
dimension = true

[[jira.issue_hierarchies]]
name = “Epic - Story - Task - Sub-task”
all_member_name = “All Issues”
levels = [
{name=“Epic”, key_column=“epic_key”, issue_type=“Epic”},
{name=“Story”, key_column=“epic_parent_key”, issue_type=“Story”},
{name=“Task”, key_column=“customfield_story_link”, issue_type=“Task”},
{name=“Parent”,key_column=“subtask_parent_key”},
{name=“Sub-task”, key_column=“subtask_key”}
]

Any help appreciated!

2

Hi @Paul1,

The issue is that sub-tasks need to inherit the custom link field value from their parent Task. You can fix this by adding update_from_issue_key = "parent_issue_key" to your custom field definition:

[jira.customfield_story_link]
name = "Story (via link)"
outward_link = "is parent of"
issue_type = "Task"
dimension = true
update_from_issue_key = "parent_issue_key"

This tells eazyBI to pass down the “Story (via link)” value from Tasks to their sub-tasks, so sub-tasks can be correctly placed under their parent Task in the hierarchy.

After updating the advanced settings, re-import the data and the sub-tasks should appear under Tasks as expected.

See Additional Issue hierarchies documentation

I hope this helps!

Best,
Marita from support@eazybi.com

3

Hi Marita,

Thank you very much for your response.

Unfortunately, the fix doesn’t work:

image
image918×498 33.5 KB

[jira.customfield_story_link_test]
name = “Story Parent”
outward_link = “is parent of”
issue_type = “Task”
dimension = true
update_from_issue_key = “parent_issue_key”

[[jira.issue_hierarchies]]
name = “Test hierarchy”
all_member_name = “All Issues”
levels = [
{name=“Epic”, key_column=“epic_key”, issue_type=“Epic”},
{name=“Story”, key_column=“epic_parent_key”, issue_type=“Story”},
{name=“Task”, key_column=“customfield_story_link_test”, issue_type=“Task”},
{name=“Parent”,key_column=“subtask_parent_key”},
{name=“Sub-task”, key_column=“subtask_key”}
]

I’ve re-imported all issues multiple times but still no Sub-tasks in the report. The Sub-task has been imported and visible when displaying all issues:

image
image718×106 7 KB

Can you suggest another solution, please?

Regards,
Pawel

4

Hi @Paul1,

Apologies for the delay in response.

The issue is that the hierarchy configuration needs an adjustment to correctly place sub-tasks.

The main change needed is to switch from outward_link to inward_link for your story link field - the link should be defined from the child’s perspective (Task “is child of” Story).

Here is the updated configuration to try:

[jira.customfield_epic_link_test]
name = "Epic Link Test"
inward_link = "has Epic"
issue_type = "Epic"
dimension = true
update_from_issue_key = "customfield_story_link_test"

[jira.customfield_story_link_test]
name = "Story Parent Test"
inward_link = "is child of"
issue_type = "Story"
dimension = true
update_from_issue_key = "parent_issue_key"

[[jira.issue_hierarchies]]
name = "Test hierarchy"
all_member_name = "All Issues"
levels = [
  {name="Epic", key_column="customfield_epic_link_test", issue_type="Epic"},
  {name="Story", key_column="customfield_story_link_test", issue_type="Story"},
  {name="Task", key_column="subtask_parent_key"},
  {name="Sub-task", key_column="subtask_key"}
]

Make sure both new custom fields (“Epic Link Test” and “Story Parent Test”) are selected for import in the eazyBI data source import options. After updating the advanced settings, perform a full re-import.

See Additional Issue hierarchies documentation

Best,
Marita from support@eazybi.com