Currently the "features" and "master features" relate to work output, not actual product concepts that users care about.
tl;dr; please give us more ways to separate concepts from the actual work. Features should technically be conceptual, and should be linkable to work, but Aha! forces you into work-oriented representations of features with its current data model.
There was an attempt to answer this problem with "master features" (see https://big.ideas.aha.io/ideas/APP-I-605), however, it just created yet another larger work bucket item. The problem is that all of the Aha! data model goes from product/vision directly into date oriented concepts, with no room for conceptual things like features or components.
Currently, the workaround to all of this is to create a custom field and populate that with the values of the features/components that should live in your product. However, there are two issues with that:
Example: my product is a "phone" app on android, one of the features is call history, here's what I'd like to see in the aha data model
Without the call history feature theme, it's difficult to understand things like "what are all of master-features and features that relate to the actual logical feature: call history. Yes, you could ask me to create tags or custom fields around this, but then again the problem remains that Aha! doesn't give me good ways to visualize and understand my roadmap in terms of features by collection except by MORE custom pivots, etc.
Another alternative solution is to allow us to create and report on relations to features. E.g. v2 relates to v1 and everything in anchored or linked to the next version. This might be more complicated but I'm open to ideas here. Hope this makes sense.
|Release time frame|