Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, feature)
Thank you for your idea. We do not currently have plans to make changes here but we will continue to monitor feedback on this idea. In the meantime, we would suggest using bulk edit to send multiple features at a time to Jira. From the features list, you can filter by feature type, select the features, and send them as the correct issue type you would like them to map to in Jira. We hope this helps in the meantime.
I suggest to allow Types at Feature and Requirement Level which allows to map them with different issue types in the ALM (Jira, Azure DevOps), with this it will be possible to mirror Bugs, Enables, Technical Dept, etc in Aha and track it in the release Gant.