I am (cloning and) moving an issue using (ClonePlus Plugin) Clone++ from Project A to Project B. Project B has issue security scheme enabled and has a default security level defined. I do not have set security level permissions on Project B.
In this scenario, during Clone++ operation i do not see the security level field, which is expected as i do not have permissions. But the bug i am facing is that after moving, the issue has None as the security level instead of the default security level.
How can we get around this bug?
If i create use the move operation which is jira's in-built feature then the bug cannot be replicated.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs