I know this question has been asked a few times here however the suggested solutions do not work for us. We've been trying to use the Workflow Properties to restrict access to cloning however it doesn't seem to recognize the command. The properties that we've used so far:
You may be interested in this open suggestion with Atlassian on Clone permission that has been around since 2005.
As a requirement it has not yet received many votes and so will not be highly featured on the list of desired functionality for Atlassian.
There is a workaround in here to disable the Clone link that you could try but as this will then remove it from the instance that may not be an appropriate solution.
As commented by @Mark McCormack you can use ScriptRunner for JIRA to also hide system/plugin UI elements based on conditions but that would require you to have this plugin installed in your system.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
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