I'd like to be able to add a new feature to a master feature and have it inherit info like Aha! score, custom fields (e.g. customer, market, initiative), etc.
You can now create an automation rule to copy the initiative of an epic to all its child features. We will keep this idea open to monitor feedback for the other fields that you would like to see inherited.
Yes! Having to create custom fields in duplicate for features and master features, as well as maintain any updates to each independently (e.g. adding a choice) is a frustration and creates considerable potential for error and inconsistency.
+1. If this is implemented hopefully all metadata gets inherited, but if it's only a subset then Watchers should definitely be one of the fields that gets inherited.
This is a huge usability issue for us and we look forward to a fix.
Yes! All of our features have master features. Because of the work involved to re-fill out all of the fields in the features, most features are missing field values that are critical to reporting. There are 5-8 fields that need to be filled out with every feature creation that could be inherited. It would be great to be able to define the fields that are inherited from the master feature by default, with the opportunity for the user to change prior to submit. A huge time savings!!