We have initiatives with child initiatives and those child initiatives contain releases, epics and features. The child initiatives are in a separate workspace line from the parent initiatives. The Strategy>Initiatives>Roadmap view works fine for the child initiatives and this view shows the associated releases, epics and features. However, this view does not allow for the additional layer of parent initiatives and there is no other way to accomplish this view. It would be helpful to show parent initiatives on the report as well, with child initiatives and their child records nested underneath.
This would be great! We have parent initiatives in our business line, which split into (product-specific) child initiatives, which contain epics.
Take the following hierarchy:
Business Line Initiative
Product 1 initiative
Epic A
Epic B
Product 2 initiative
Epic C
Epic D
Right now if I want to visualize a strategic roadmap for the business line, I will see Business Line Initiative but that won't show the child initiatives or their epics. Note that this type of visualization is extremely useful to visualize dependencies across products/teams, and in general which work is being done across the org for a specific effort.
The only way for me to do that is to have Epics A-D all linked to the Parent Initiative, but still under their respective product workspaces, and delete the child initiatives. This is fine conceptually - however, it creates another problem: When I want to generate a strategic roadmap for Product 1, I can include initiatives from Business Line, including Business Line Initiative. This will show me (correctly), Epics A & B under that initiative, but will also show Epics C & D, which are underlated to Product 1. Note that, at this time, there seems to be no way to filter out epics by workspace in the strategic roadmap. ( This latter is probably another idea )While this is somewhat possible by building a custom roadmap, all the nice visualizations of hierarchical relationships, and the ability to edit timelines on the fly are lost.
Solving either of the issues highlighted above would be a huge help for organizations with larger product portfolios!
Our product managers are using Aha in Scaled Agile Framework mode so Initiatives map to Epics and it is usual to have parent and child epic relationships, hence the requirement.