Fix version not populated in the "Version picker" custom field when the Automation rule is triggered by a JSM project

Issue Summary

When an Automation rule is triggered by a JSM ticket and it tries to create an issue in a JSW project, the fix version field is not populated. If the field is required in the JSW project, the rule will fail.

Steps to Reproduce

1. Create an Automation rule that will be triggered by any issue event in a JSM project
2. This rule will create an issue in a JSW project
3. In the create issue action, add a custom field of the type "Version picker"
4. Select any value from the options in the drop-down, for example, last released version, or a specific version.

Expected Results

The version information should be updated in the field during the issue creation.

Actual Results

The field is not updated (remains empty) and, if it is a required field, the rule will fail with a "field is required" error in the logs.

Workaround

Set the field as optional in the project where the issue is being created.