Permission for cloning issues

[S]

Hi,

Can we restrict any user from cloning issues in jira.

-Shruti

[Bob Swift OSS (Bob Swift Atlassian Apps) · Accepted solution]

JIRA Clone-Plus Plugin has options for controlling when the clone operation shows up on the UI for users including group control. You will need to hide or disable the system clone operation - see How to customize for more details.

[David Skreiner]

No need for expensive plugins.

1. Open the workflow
2. Open each workflow status and click "Properties"
3. Add the property key jira.permission.create.clone.denied to each workflow status
4. Publish the workflow

Issues using this workflow can now lo loner be cloned. The button is still there, but users get an error message if they use it.

[Thomas Schlegel]

No, I don't think so. If a user is allowed to create an issue in a project, he is also allowed to clone an issue.

Best regards

Thomas

[Rickard Schoultz]

Cloning an issue causes all sorts of problems when working with other plugins that has registered some kind of external ID and synchronizes back and forth to JIRA. Now one gets two issues with the same ID, and then we lose the connection between the synchronized system and JIRA.

We really need to be able to turn this off.

[Bob Swift OSS (Bob Swift Atlassian Apps)]

Remove the option from the UI as mentioned in my post above.

[Laura Franco]

How about removing Link Issue permission for the project role? Would that prevent those users from being able to Clone since a Link is part of Clone action?

[MattS]

You could write a custom condition and add it to the definition of Clone in system-issueoperations-plugin.xml

Or add a custom validator to the Create transition of the workflows in question, though I'm not sure if this wouldn't leave the original issue with a dangling link.

Probably the easiest way to do this would be to add some JavaScript to the view issue page to disable the Clone operation when required.