Some of the features we're developing will support more than one master features. Currently there is a limitation that a feature can support one and only one master feature. This falls short for us and doesn't allow us to see where investment in one feature provides a return on investment in multiple use cases.
Thank you for your idea. One idea here would be to add a master features custom field using a an Aha! record relationship field -- for example "Secondary master features." The record relationship fields will automatically be populated with records from your Aha! account, so your master feature names would automatically be available.
At this time, given the option above and other priorities, we are unlikely to implement this idea. We hope you can understand.