RELATED IDEAS
Add Phases and Milestones to Initiatives
As a user of Aha, I want to be able to add phases and milestones to initiatives, so that I can track important work streams relating to an initiative.
Today, the only way to track work streams, phases or milestones is to create a release. However, as a Product Manager I have activities that are related to initiatives. For example, my Initiative could be to scale my product internationally which might involve several releases, as well as activities that are not part of a product release such as Marketing efforts, Business Case Sign off.
At the moment, I have to create a release purely for the product release, then create a separate 'release' for the other activities that span several releases, simply so I can track those activities.
This feature would really allow me to embrace Aha much more.
-
ADMIN RESPONSEJan 24, 2018
Thank you for your idea. Customers often handle this using their product hierarchy. More specifically, you can add the initiatives at the product line level and then create a second product where you manage work that is related but not a direct part of the product release. Releases in both products can then be mapped to the product line initiative. This provides the added benefit of assigning work to others on the team who may not have or need product owner or contributor permissions in the other product.
Based on the capabilities described above we are unlikely to implement this idea at this time.
I find it somewhat surprising that the initiatives board, the "highest level" of strategy board, would be the board where my tools and view is intentionally narrowed. According to the documentation Phases/Milestones are allowed on Gantt boards at the Releases level. https://www.aha.io/support/roadmaps/videos/aha-roadmaps-overview/plan-releases
These items are actually already available on the Initiatives board, they are just automatically deleted on refresh (saved or not). See the attached image (edited with sensitive data removed).
I'm still trying to understand why the functionality, which actually appears within the strategy roadmap view today, is being removed? I understand what Admin indicated above, but why not leave an existing feature that some users find helpful?