Jira Product Discovery is a new tool for PMs to create product roadmaps. It introduces a many-to-any custom hierarchy that EazyBI currently does not support because an issue type can be on multiple hierarchy levels.
For example this is a normal issue hierarchy in Product Discovery
Idea
|- Epic → Task → SubTask
|- Idea → Epic → Task → SubTask
where Idea can exist on top level and also be a sub-idea. Same goes where Epic can be directly linked to the top idea or be linked to the sub-idea
Idea uses “subtask” type of IssueLink to indicate idea → sub-idea hierarchy relation and “implements” type of IssueLink to indicate the “Delivery ticket” relation aka Epics, Tasks, Stories etc any kind of Jira issueType that “delivers” or contributes to the idea
There is no limit what can be a “Delivery Ticket”.
Are there any plans of including this type of dynamic custom hierarhy support to EazyBI?
Or maybe there is already a way to set up this kind of custom hierarchy?
Hi @sandervall,
Efficient reporting in eazyBI is achieved by categorizing issues and aggregating values over issue categories and hierarchies.
If the same entity can appear in several hierarchy branches, it inevitably leads to value multiplication and exaggerated totals.
Therefore, eazyBI supports straightforward strict hierarchies that allow aggregated values to be calculated over hierarchies as well as categories during data import.
Hierarchical structures that allow certain hierarchy levels to be skipped or the same issue type to be on different levels tend to turn into meshes and create circular references.
Currently, there are no plans to introduce dynamic hierarchical structures that could lead to less reliable data or break data cubes.
Each hierarchy has to be consistent within the use case. You might as well use several hierarchies of the same dimension within one expression, but you then need to deeply understand the context in each calculation step.
It could be possible to build two hierarchies and use them in the same report if the Idea and sub-idea have different issue types.
Some reports could also be built using issue links on top and consistent hierarchies underneath. Still, each workaround used to handle deviations from strict hierarchies leads to more complex expressions and reduced calculation efficiency.
Regards,
Oskars / support@eazyBI.com
Hi @oskars.laganovskis
Thank you for the detailed explanation. I totally understand the reasons and why it should be strict.
The challenge for me here is that PM-s tend to choose shiny tools what they like 
And it becomes rather quickly my problem when they lose reporting capability
My prediction is that Jira Product Discovery will pick up steam and will replace Advanced Roadmaps pretty soon because it is way more flexible, fast and visually pleasing