Clone issue option does not show for any issues in Jira Data Center
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
The Clone option does not appear in the ... (More options) menu for any Jira issue.
Check for workflow properties or the Issue Operations plugin module
It's possible to disable issue cloning using the workflow property, jira.permission.create = denied
.
This workflow property may also be written as jira.permission.createclone
or jira.permission.create.clone.
Jira will read all of these the same way, and all will prevent the creation of new issues during this workflow step, including issue cloning.
Please refer to this article for more details: How to restrict issue cloning in Jira
You can review your workflow steps to check for this property, or query the Jira database:
select * from jiraworkflows where descriptor like '%permission.create%';
This SQL query returns any workflows that have this property setting. If Workflow properties are set to restrict creation, they must be removed from the Workflow to allow for cloning.
Also, there is a System Add-On, Issue Operations Plugin, which has a module called View Issue Ops Bar Clone Link. This module controls whether the Clone option is available for the entire instance, and needs to be enabled to allow issue cloning.