Issue Summary

When cloning issues between two JSM projects using same Screen Scheme, Issue Security Scheme and Issue Type Scheme does not set the Issue Security Level for the new (cloned) request. The default Issue Security Level in the project is not set in the new request.

Steps to Reproduce

• Create an automation rule to clone a request from one project to the other. Set default Issue Security level for the Issue Security scheme used by both the projects

• Select Security Level to be set when cloning the issue.

• Execute the Automation Rule to clone the request into the other project
• The Issue security level is not set for the new cloned request but present in the Original request.
  • Original request 

• • Cloned request

Expected Results

Issue Security Level should be set using the value set in Automation Rule or using the default Issue security level configured on the Issue Security Scheme.

Actual Results

Issue Security Level is not set for the cloned issue.

Workaround

After using Clone Issue into action, use Edit Issue Fields component and set the Issue Security Level for the cloned issue