It is so aggravating that this was left out. I want to use master features so badly, but I can't visually communicate out about them in my existing roadmaps. The reporting is keeping me away from what could be a great feature.

See below chat.....speaks for itself I think. Thx for giving this more votes.

Tom Bailey(Aha! Support)

Oct 6, 01:44 PDT

Hi Nicolas, Thanks for your note. Unfortunately Master Features are not available on the Starter Roadmap. To make a suggestion you can request this on our idea portal where our product team can review your suggestion directly: https://big.ideas.aha.io/ Many thanks.

We spent a day or two entering in master features into Aha because the support articles and documentation recommended that master features should be used like Epics. Epics are the right level of detail for a roadmap and the starter roadmap is the report that would let us build the kind of roadmap representation we are looking for. To workaround this limitation, we will need to re-enter 2-3 years of epics into Aha, significantly reducing the ROI of this tool. Would have been good if the documentation had either warned in appropriate places or not recommended using master features as epics altogether.

We are using master features as Epics. It was a bummer when we found out that we can't show these epics in the roadmap. Master Features are pretty useless for us if we can't build a graphical representation in the roadmap. I hope this is a feature that gets implemented soon.

It would be great that, once you add a Master Feature to the Starter Roadmap, users have the ability to expand the Master Feature to see the child Features (much in the same way that you can expand a Release to see what is under that Release). This gives the user the ability to "drill down" from the Release, to Master Features, to Features, as needed. Being able to expand a Feature to see its child Requirements would be an added bonus.