I was thrilled when the new Strategy Roadmap feature was added to Aha....until I realized that it won't work for us. From the release notes:
"Use the new Strategy -> Roadmap view for doing top-down, longer range planning and highlight your major roadmap themes."
This sums up what for me was the biggest missing piece in Aha. However, we have Initiatives mapped to Epics in JIRA and Features mapped to Stories. Our developers rely on the Epics groupings to keep their work organized, so not having a field in Aha that can map to Epics is a problem. But using the initiative field for Epics means that the strategy roadmap is really meaningless since it will show pieces of projects and not true initiatives.
Maybe there is a better way to set up Aha to get the best of both worlds? Would love some feedback on this.
|Release time frame|
Today, we have introduced Master features -- a powerful new capability for your bigger work items. You can use Master features as another level in between your existing strategic initiatives and features, where you can group multiple features that span across many sprints or releases.
Read more about it in out blog post: https://blog.aha.io/epic-roadmap/
Please note -- Master features are not immediately supported by our integrations, but we are working hard to add that functionality in the near future. So keep that in mind — they are not supported by our integrations right now.