How to configure problem clone permissions?

Question

Cloning problems will clone the values of user-defined fields at the same time, which will lead to problems in statistics based on some user-defined fields, which are very important, so we urgently need to withdraw the permission to clone problems.

If the permission to reclaim cloning problems is not currently supported, are there other alternatives? For example, some custom fields are restricted from being cloned at the same time. Or is there a plug-in that can recycle permissions?

Thank you. Looking forward to your reply.

Marlene Kegel - codefortynine · Answer

Welcome to the community, @王钦.

I am Marlene from codefortynine.

It seems that disabling the standard clone feature is only possible in Jira Server and Data Center:

* https://confluence.atlassian.com/jirakb/disable-clone-issue-in-jira-747836996.html
* https://community.atlassian.com/t5/Jira-questions/How-to-disable-the-cloning-of-issues-using-jira-cloud/qaq-p/1004306
* https://jira.atlassian.com/browse/JRACLOUD-8497

I'm not sure if that would help in your case, but with our app Deep Clone for Jira you have more flexibility in changing permissions of cloning - unfortunately permission changes only affect our app, not the standard Jira clone functionality.

In Deep Clone you can e.g. restrict cloning attachments, comments and work logs. It's also possible to restrict cloning for certain users or into certain projects.

You can read more about permissions and restrict access in our documentation.

Also feel free to reach out to our support, if you need to know if it is possible to prevent users from cloning a specific field.

王钦 · Answer

Thank you for your reply.

Do you know how to reclaim clone permissions? That is, the user cannot see the copy button and cannot copy.

Nic Brough -Adaptavist- · Answer

Welcome to the Atlassian Community!

Yes, cloning does what the name suggests - makes a copy of the current issue.  There's no way to change what it does because it wouldn't be a clone if you changed fields.

If you think you want to change fields during a clone, then you're actually looking in the wrong place - you should be creating a new issue, not cloning.