Basically, we’re using a pretty standard hierarchy in Jira and Advanced Roadmaps, which looks like (top down):
Initiative → Feature → Epic → Task → Sub-Task.
I have the Parent Link (for Feature to Initiative) and Parent Link (for Epic to Feature) and Epic Link (for Task to Epic) in place…see the screenshot.
I use this definition in my settings but not working: #setup issues hierarchies
[[jira.issue_hierarchies]]
name = “Initiative”
all_member_name = “All Issues by Initiative”
levels = [ #two custom levels above default epic hierarchy
{name=“Initiative”,key_column=“customfield_Initiative”,issue_type=“Initiative”},
{name=“Feature”,key_column=“customfield_feature”,issue_type=“Feature”}, #default set of levels for epic hierarchy, do not change it
{name=“Epic”,key_column=“epic_key”},
{name=“Parent”,key_column=“epic_parent_key”},
{name=“Sub-task”,key_column=“subtask_key”}
]
But the task does not appear, neither the sub-task.
Please, let me know. what is wrong? And why the feature & sub-task aren’t appear
Regards
Hi @jdavila
In case you are using Advanced Roadmaps, you need to select Parent Link and Epic Link fields in the import options and then during the import the additional hierarchy is created based on the Advanced Roadmap configuration (on the Cloud you need to enable the integration and add the hierarchy configuration, see here )
[[jira.issue_hierarchies]]
name = “Initiative”
all_member_name = “All Issues by Initiative”
levels = [ #two custom levels above default epic hierarchy
{name=“H Initiative”,key_column=“customfield_initiative”,issue_type=“Initiative”},
{name=“Feature”,key_column=“customfield_feature”,issue_type=“Feature”}, #default set of levels for epic hierarchy, do not change it
{name=“Epic”,key_column=“customfield_epic”,issue_type=“Epic”},
{name=“Task”,key_column=“customfield_story”,issue_type=“Task”},
{name=“Parent”,key_column=“subtask_parent_key”},
{name=“Sub-task”,key_column=“subtask_key”}
]
Thanks