Releases incorrectly default when creating Master Features and Features.

When building out initiatives, master features and features created are defaulting to the nearest term planned release. Even if this release is not linked to that initiative. This is causing master features and features to be inadvertently assigned to active releases creating issues with our Jira integration and extra effort correcting them after the fault has been discovered.

This behaviour is backwards.
When building out initiatives, they should be broken down into master features and features, then releases created, to deliver the incremental value of those initiatives.

If subsequent to this additional master features and/ or features are identified for an initiative they should only be able to be assigned to a release associated to that initiative, or to a new release.