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.
© 2025 Aha! Labs Inc.•All rights reserved
Adding an additional comment here to possibly revisit this idea. With the growth of Teamwork, and therefore some organizations bringing on non-tech teams and deliverables associated with GTM strategies, implementing phases and milestones at the initiative level is incredibly helpful. Building additional releases related to initiatives makes sense, but phases/milestones of an initiative might be different than a true release/project/schedule of an initiative for non-tech teams.
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?