Epic/Feature boards using custom fields than versions

What is the challenge?

Today we are not using Aha! out of box Releases and using a custom field for Release at Enterprise wide. So existing Aha! boards is forcing us to create versions at workspace but ideally we would like to use our custom field as Release.

What is the impact?

We are creating versions which is not used for us. Users are not able to view by Custom Field of Release.

Describe your idea

Today we are not using Aha! out of box Releases and using a custom field for Release at Enterprise wide. So existing Aha! boards is forcing us to create versions at workspace but ideally we would like to use our custom field as Release.