Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Can I prevent users from cloning issues on a specific project?

I am building a project which will be used internally for Code Releases i.e. this will not be a typical Software Development project. I want to prevent users from cloning issues, is it possible to do this for this project only?

4 answers

1 accepted

4 votes
Answer accepted
Ignacio Pulgar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Dec 08, 2017

You can potentially do it by applying this property to all workflow steps used by the project:


Ensure the workflows in which you add this property are not used by any other projects; otherwise the clonation would be forbidden in other projects too.

This does work and must be applied to all statuses on that workflow. Luckily, in my case, this was a small project that was using it's own workflow so this worked perfectly.


Like Karoline Rezende Ramos likes this

Hi @Ignacio Pulgar

In my software project, we have given access to 'Anyone' to create issues. If I need to restrict 'clone' option to 'Anyone'. What should I enter in Property.

Please suggest

Ignacio Pulgar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 20, 2020

Hi @Sreekala Dande ,

For not allowing the creation of clones to Anyone, you need to add a property which allows the creation of clones just to users with either a role in the project, or a jira group.

Probably, your use case should be better covered with roles, so this is the property you need to add on all statuses of your workflow, specially the initial status (please, see JRASERVER-62200 for more info on this subject).

jira.permission.createclone.projectrole = 10300

Where 10300 is the id of the project role you would like to retain the ability to clone issues.

As far as I've tested, both createclone and create.clone are valid and equivalent syntaxes.

You may find the id of a given project role in the URL shown after clicking on its Edit link, on the Project Roles Browser.

First, go to https://YOUR_JIRA_BASE_URL/secure/project/ViewProjectRoles.jspa


Click on Edit and see the id of a project role, in example Administrators:


As you are likely to need to enable the creation of cloned issues to more than one project role, then you will need to add a numerical suffix at the end to make each property unique, like this:


You may also learn more about the usage of workflow properties by visiting this article.

Hope it helps.

Like # people like this does a very good job of describing why this is a hack (and why "createclone" and "create.clone" and in fact "" all "work" the same).

Apparently Atlassian acknowledges this method is a hack and apparently has no intention of adding a feature to officially restrict cloning of issues.

The key used here, jira.permission.create.clone.denied, is invalid, and JIRA is just throwing a valid error:

Unknown type 'clone' in meta attribute 'jira.permission.create.clone.denied'. Valid permission types are defined in permission-types.xml

Using the right key, jira.permission.createclone.denied, the problem shouldn't happen.

As stated in bug 59487

You can take away rights for them to create issues, but cloning is not an available action to be controlled in permission schemes. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events