Moving an issue to a resolved state can leave the resolution empty

Steps to reproduce

1. associate project A to workflow A, which has To Do, In Progress, and Done statuses
2. associate project B to workflow B, which has Open, Reopened, In Progress, Resolved, and Closed statuses
3. make sure status Resolved in workflow B requires a Resolution on the Resolve Issue screen
4. create a new issue in project A, which should have status To Do
5. move it to project B and select status Resolved

Expected behavior
Resolution field should be required to be filled in in the Update Fields step

Actual behavior
Resolution field is not required to be filled, resulting to the fact that the issue is Resolved without a Resolution

Original description

When moving an issue to a context that does not contain the current status, you can select a new status. E.g. "Awaiting Review" -> "Resolved"
This moves the issue into the resolved state, however the issue does not have a resolution. You need to re-open and then resolve it to be prompted for a resolution.
As resolution is not a required field, this is not technically a bug but still can leave JIRA in an inconsistent state. A bit like not having the resolution field on a the resolve transition screen.

This happens for move issue and convert to subtask/issue.