When cloning an issue through Automation rule, security level value is copied even though the security level is not available in the created issue's project

Issue Summary

When cloning an issue through Automation rule, the security level is copied even though this is not applied to the destination project, what makes the created issues unaccessible.

Steps to Reproduce

1. Create a security scheme and apply this to project A
2. Create a security scheme and apply this to project B
3. Build an Automation rule using Clone action, being issue from project A the trigger issue and cloning this to project B
4. Make sure security level is applied to the trigger issue and that this security level is not applied to project B
5. After the Clone Issue action, add a Most recently created issue branch and within this add any action as Log Action, for example
6. Automation rule won't be able to find any issue within branch even though an issue was successfully created by the rule

Expected Results

Since security level is not applied and available in created issue's project, an error message should be shown and issue should not be created.

Actual Results

When cloning the issue in project B, the security level value is copied even though this is not available in project B. Due to this, the created issue is unavailable to be accessed, even though the user has the needed permissions.

Workaround

Two approaches to mitigate this:

1. If the destination project is using an Issue Security Scheme as well, specifically set a level during the clone action that is accessible in that project
2. Clear the value using smart values during the clone action

More granular information on the above can be found in the following KB:

• Cloning issues with Issue Security Scheme levels via Automation