# Nesting Products and Milestones within Existing Jira Hierarchy

**URL:** <https://community.eazybi.com/t/nesting-products-and-milestones-within-existing-jira-hierarchy/19707>\
**Category:** Questions & Answers\
**Tags:** javascript, dataimport, hierarchy, eazybi, mdx\
**Created:** [March 20, 2025, 3:53pm UTC](https://community.eazybi.com/t/nesting-products-and-milestones-within-existing-jira-hierarchy/19707 "2025-03-20T15:53:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![grahamlakin](https://community.eazybi.com/letter_avatar_proxy/v4/letter/g/b9bd4f/32.png) [@grahamlakin](https://community.eazybi.com/u/grahamlakin)\
**Post date:** [March 20, 2025, 3:53pm UTC](https://community.eazybi.com/t/nesting-products-and-milestones-within-existing-jira-hierarchy/19707/1 "2025-03-20T15:53:19Z")

</div>

Hello,  
I am attempting to nest issue types: products and milestones, into my existing issue hierarchy from Jira. The existing issue hierarchy is: Initiative → Capability → Feature → Epic → Parent → Sub-Task. On the Jira side, Products and Milestones are brought into the structure via Child-Parent issue links (outward=is a child of, inward = is parent of). My current progress has led me to this code below, but I do not believe it is working. I would like to see the products/milestones (products right now for simplicity) underneath the respective hierarchy level as “siblings” to the level below. i.e. if a product is a child of an initiative, it will be listed on the same level with the capabilities that are below the same initiative.

```auto
[[jira.issue_hierarchies]]
name = "Gantt"
all_member_name = "All Gantt Items"
levels = [
  {name="Initiative",key_column="jpoh_parent_5",issue_type="Initiative"},
  {name="Capability",key_column="jpoh_parent_4",issue_type="Capability"},
  {name="Product", 
   calculated_member_expression = 
       "NonEmpty(
           Generate(
               [Issue].CurrentMember.Parent.LinkedIssuesByLinkType('is parent of'),
               [Issue].CurrentMember.Parent.LinkedIssuesByLinkType('is parent of').[Issue].Key,
               ', '
           ),
           [Measures].[Issues created]
       )",
   issue_type="Product"}, 
  {name="Feature",key_column="jpoh_parent_3",issue_type="Feature"},
  {name="Epic",key_column="epic_key"},
  {name="Parent",key_column="epic_parent_key"},
  {name="Sub-task",key_column="subtask_key"}
]

```

Thank you.

---

<div class="post-metadata">

**Author:** ![roberts.cacus](https://community.eazybi.com/user_avatar/community.eazybi.com/roberts.cacus/32/637_2.png) [@roberts.cacus](https://community.eazybi.com/u/roberts.cacus)\
**Post date:** [April 10, 2025, 2:42pm UTC](https://community.eazybi.com/t/nesting-products-and-milestones-within-existing-jira-hierarchy/19707/2 "2025-04-10T14:42:39Z")

</div>

Hi @grahamlakin,

You seem to have reached out to the eazyBI support directly as well. In that conversation, I pointed out that the current issue hierarchy definition doesn’t work because of the “Product” level definition. The expression below is not supported when defining hierarchy levels:

```auto
calculated_member_expression = 
       "NonEmpty(
           Generate(
               [Issue].CurrentMember.Parent.LinkedIssuesByLinkType('is parent of'),
               [Issue].CurrentMember.Parent.LinkedIssuesByLinkType('is parent of').[Issue].Key,
               ', '
           ),
           [Measures].[Issues created]
       )",

```

Please see the following example, where the “Story” level is introduced between Epic and Parent levels. You would have to define the links linking all the levels above the sub-task parent level. Additionally, an issue type can be used only on one level, not multiple.

Kind regards,  
Roberts // [support@eazybi.com](mailto:support@eazybi.com)