RELATED IDEAS
Ability to roll up Initiatives to multiple parent initiatives
We need to be able to roll up initiatives to multiple products. Right now, when you link to a product or product line, you are only allowed one link. Based on how we need to roll up and generate reports, there was no workaround that would do the trick.
-
ADMIN RESPONSEJan 29, 2016
As noted, current capabilities allow for initiatives to roll up to a single initiative up the product hierarchy. The reason for this is to show the clear path and strategy links across products and product lines.
At this time, due to current priorities, we are unlikely to make updates in this specific area. We hope you can understand.
© 2024 Aha! Labs Inc.•All rights reserved
I am concerned that a common use case is not being supported. At both the EPIC-Initiative and Initiative-RollUp-Initiative levels, there should be the ability to have multiple parents. In my experience, product managers aim to have a single piece of work impact as many "parents" as possible on lower levels. For example:
• one EPIC impacting multiple project (initiative) deliveries
• one Initiative contributing to multiple higher level goals
• and so on.
I will echo the previous sentiments. We set company goals, and want to cascade them down to workspace goals. Many times, team goals support more than one company goal and we'd like that represented in our reports. Currently we simply can't capture this in Aha! and teams are reverting back to spreadsheets (GASP) to represent it.
I agree, cross-product features are something I think would be really useful in all containers of Aha, as often my team plans work this way since many of my products are related and worked on by the same teams, such as engineering. Thanks!
Being able to roll initiatives up to multiple parent initiatives would definitely help my organization manage situations where the work happening at a product-level is actually supporting multiple initiatives at the company-level.
Using a custom field for this is causing a lot of confusion and effort to ensure users in out org are properly trained. Universal dependencies would be fine if there was an option to see a timeline/roadmap view; but that doesn't exist.
At this point, the "best" option that our users default to is misuse of goals. It's effective, but not ideal.