Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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?

2 answers

1 accepted

1 vote
Answer accepted
Ignacio Pulgar Community Leader Dec 08, 2017

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

jira.permission.create.clone.denied

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.

Thanks
Mo

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 Community Leader 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

edit-project-role.PNG

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

project-role-id.PNG

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:

createclone.PNG

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

Hope it helps.

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
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you