We are using Jira Cloud and are using the Plans. Within this we have an issue hierarchy setup for SAFE following Value Stream, Epic, Initiative, Feature, story/bug/task, Admin/development/testing (Subtasks).
For features, they are the standard Jira epics, and the links to stories etc and subtasks are fine, but I cannot find the link type that plan uses to create the parent and child links between Value Stream, Epic, Initiative and Feature, so am struggling setting up the correct advanced fields to represent this correctly.
Would anyone have done this and have the answer? What could the settings for this setup be and what would the Parent Link and Child Issue links be called for the setup?
eazyBI does not have full support for Advanced roadmaps (formerly Jira Portfolio) in Cloud. We do not have an access to hierarchy setup, therefore, we can’t read all the levels and define a hierarchy.
Here is an example for two levels Value Stream and Initiative above Epic (Value Stream>Initiative>Epic>Parent>Sub-tasks). In this example, I will use the default issue type Epic pulled in by Epic Link custom field in Jira. If you are using any other issue type instead of Epic with Epic link, you would need to override this level as well.
Here is an example definitions for this:
Daina / email@example.com
eazyBI can’t detect portfolio hierarchy configuration in Cloud by default. We added support Advanced Raodamp data and hierarchy import with additional configuration on Cloud. You would like to specify the hierarchy levels and issue types per each level as you have in Jira. We will import a hierarchy based on this configuration.
Daina / support@eazyBI.com