When using Clone++ operation (ClonePlus Plugin) security level defaults to None instead of setting Default security level

Hi Everyone

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.


1 answer

1 accepted

Are you on a current release of the add-on? It should work - see JCPP-220. Open another issue if you are on a recent version and it is not behaving as expected.

Thanks, yes this works.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

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 ...

397 views 6 0
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you