The discrepancy in the behavior of the Release option

With further testing we noticed releasing issues using Release from Project menu > Releases > (...) > Release depends on whether there are any issues in the status other than Done Category.

Steps to reproduce this issue:

With no resolution set and having a few incomplete issues:

1. Create a Release version (say V1) in the project: Releases > Create version
2. Ensure Resolution is not added to the Done status
3. Add this release as a Fix version to a few issues, move a few of them to Done status, and leave a few issues in In progress or any other status
4. Create another version, say V2
5. Release V1 and move the unresolved issues to V2

Result:

No issues will be released, but the prompt showed the issues in Done status will be released.
 Release - issues in progress.mov

With no resolution set and all issues moved to Done Status:

1. Move all the issues to Done status
2. Release V2

Result:
All the issues will be released.

Release - all issues in done status.mov 

The issue is reproducible:
Only when resolution is not set for the statuses belonging to Done Category and there are unresolved issues in the current release.

The issue is not reproducible:

1. When the resolution is set for the statuses belonging to Done Category and if there are unresolved issues
2. When the resolution is NOT set for the statuses belonging to Done Category and if there are no unresolved issues in the release.

Workaround:

Use Release Hub to release the version 

1. Run a search query that will bring all issues in the Done column that needs to be released
2. Bulk edit them to set a resolution.
   OR
3. Create a post-function on your workflow on the Close/Done transition to the "Update field" to set a proper resolution
4. Run a search query that will bring all issues released and bulk transition then through this status again.