Hi,
We need your advice on a Jira/eazyBI hierarchy use case.
Our target structure is:
Epic → Feature → Story
However, some Features currently do not have an Epic. In those cases, we use the Jira link “is connected to” to associate the Feature with another Feature. Other issues still use the standard Jira Parent field.
We would like to create one eazyBI report with a single expandable hierarchy that combines:
- the standard
Parent relationship;
- the
is connected to relationship when the standard Parent field is empty.
We understand that eazyBI hierarchies generally require one strict parent-child relationship per level. Could you confirm whether there is a supported way to achieve this using:
- a calculated JavaScript custom field;
- additional Issue hierarchies;
- a custom
key_column;
- or another eazyBI configuration or MDX approach?
The expected result is one report where Story Points and issue counts roll up correctly from Stories to Features and then to Epics, including Features temporarily linked through “is connected to”.
If this is not technically supported, could you please confirm the limitation and recommend the most appropriate workaround?
Hello @Mohssine_ZAHRI
Thanks for posting your question!
An eazyBI issue hierarchy needs one strict parent logic. Each child issue can have only one parent, and each issue type can be used on only one hierarchy level. The standard Parent field and the “is connected to” link are two different parent logics, so they can’t simply be combined in one hierarchy definition. In your case “is connected to” links a Feature to another Feature, which would also put the Feature issue type on two levels.
A couple of things about your use case are not clear to me yet, so could you please clarify the following?
- Is Epic → Feature → Story made of actual issue types, or only of level names in your Jira issue type hierarchy (Plans)? For example, are Features on the Jira Epic level, directly above Stories, with a custom level named “Epic” above them? The reason I ask is because in Jira Plans, the Epic level is always directly above Stories, so a Feature level can’t be placed between Epic and Story. A screenshot of your issue type hierarchy configuration would help.
- What do you expect from the Feature → Feature link? For example, Feature A has Epic X as its parent, and Feature B has no Epic. You link Feature B to Feature A so that Feature B can take over Epic X as its parent. Or should Feature B be shown as a child of Feature A?
- Can a Feature have more than one “is connected to” link?
- Are you using Jira Cloud or Data Center?
If you don’t feel comfortable sharing the additional details here, you can reach out to us directly at support@eazyBI.com referring to this Community post and with the additional details.
Best regards,
Elita from support@eazybi.com