RELATED IDEAS
Promoting a single idea to multiple features
I have a number of ideas which individually will spawn multiple features.
I also have other instances where multiple ideas will be resolved by one feature.
The second scenario can be covered by the merge/duplicate capability, however it is not possible to link one idea to multiple features?
Ideas can be at multiple levels of abstraction, some are small and can be achieved with one feature, however most are larger and will require multiple features and potentially numerous releases and iterations to complete, hence it would be very useful to be able to link one idea to multiple features.
-
ADMIN RESPONSEMar 6, 2019
Thank you for your idea. In the use case described, we would suggest promoting the idea to a master feature. The purpose of master features is to represent larger bodies of work that may take several features planned over multiple releases to complete.
Given the capability to promote ideas to master features, we are unlikely to implement this idea at this time. We hope you can understand.
I would say that promotion should be done to the object from data model of aha that is most comparable with the idea size (initiative, master feature, feature), but I would also say, that the link to the idea could be inherited to all objects ("related"), that are directly connected by parent-child relationship between initiatives / master features / features.
This functionality could be optional as a checkbox when master feature or initiative is created (configuration of behavior when child item is added), and also triggerable by a button with select view of all child items so that the relation of the idea can be enforced at a later time.
This would help a lot when you want the votes to count for each of the features spawn from a single idea.
This feature is very important to us. I feel it's a natural part of a workflow as well, one idea should be able to spawn one or more features. Thanks.
Struggling with the same issue. It's quite often then the stakeholders fill in the idea, it will create a need for multiple features.
This would be extremely useful to our Organisation for exactly the same reasons as above. At present we have to do a convoluted work around using 'Master Features'. Which leads to multiple complications when reporting out of the system.