Fields mapping between Release and Feature Merged

We often assign a release to a specific team, and use a custom field within the feature to manage this field. It is time-consuming to manually manage this field for every feature/sub-task when it can just be inherited from a similar custom field on the release. Thus having a default mapped to the release will help provide sane defaults.
 
We also have this same problem with wanting initiatives and goals to flow down to features by default, but now need to manually manage.