nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

how to restrict issue cloning per project in jira??

C_Faysal _CFcon_

i've already set up permissions to only allow issue linking, which brings "is a cloner of / is cloned by" to developers role

so far so good.

the issue can still be cloned just by selecting "Clone" from the More Actions tab

this is really annoying cause some users here are way too lazy to create a new issue from scratch...they simply clone a resolved one...

Accepted answers

Dhananjay Kale

I have tried this in workflow step's properties -->

jira.permission.create.clone = denied

Its working for me without restricting sub-task creation (took ref from here)

All comments

C_Faysal _CFcon_

i tried setting some properties per issue state...

such as "jira.permission.clone=false" or "jira.permission.link=false"

no effect...

what am i missing?

Jobin Kuruvilla [Adaptavist]

You can't disable just "cloning" by workflow properties because there is no separate permission for cloning. It looks for create permission.

Jobin Kuruvilla [Adaptavist]

You can't do it on a project by project basis unless you do some coding. i.e. add a condition to the respective web-item in system-issueoperations-plugin.xml.

Or maybe disable the system plugin and define an isue operation in your plugin along with the condition. You can make use of existing classes and jsp files.

C_Faysal _CFcon_

hmm well.

so what is the best approach to restrict "Clone" from "More Actions" or can it be removed from there?

C_Faysal _CFcon_

nice...i just disabled "View Issue Ops Bar Clone Link"

from system issue operations...

thats enough.

Thanks Jobin

Bob Swift

Sounds like you have an answer for your situation. For others, the Clone Plus Plugin for JIRA has a number of customization options which would allow restricting cloning to specific projects. More over, providing project specific clone options to fit better user needs. More info: How to customize

Dhananjay Kale

I have tried this in workflow step's properties -->

jira.permission.create.clone = denied

Its working for me without restricting sub-task creation (took ref from here)

Dattatray Borude

Yes, DJ it worked for me too.

Dattatray Borude

DJ`s solution working... jira.permission.create.clone = denied

Aaron Sterr

We have similar issues with cloning In a couple of projects. Users clone an issue, but then do not have edit permissions to modify key details. We have good reasons for not granting edit permissions in those projects and we expect our users to "remember" that they should not clone in those projects.

I understand that clone would not be permitted if we remove the "create issues" permission, but we do want our users to be able to create new issues in those projects.

Would it be possible to make the "clone" action depend on both "create issues" and "edit issues" permissions?

That would solve most of our problem with regards to cloning.

Thank you,

Aaron

David Skreiner2

No need for more expensive addons. Just adding the property jira.permission.create.clone.denied to every status in the workflow seems to do the trick just fine.

roniz

Dhananjay Kale,

I want to deny cloning only in a specific project in jira. Is this possible in this way?

roniz

David Skreiner

I want to deny cloning only in a specific project in jira. Is this possible in this way?

Dhananjay Kale

Yes. But need to make sure that workflow is not shared between the projects.

roniz

Yes- different workflow!

where should I define this sentence?

(jira.permission.create.clone = denied)

and where should I add the project's name?

Deepali Bagul

Hello @roniz,

Just add the properties jira.permission.create.clone = denied to the workflow/s of the specific project. Make sure the workflow is not share by other project. It worked for me.

Artsiom_Tverdakhleb

jira.permission.create.clone.denied

Paul.Young

In current (cloud) Jira, the solution to block cloning for all is:

Property Key: jira.permission.createclone.denied

Property Value: true

Christian Mendez

This worked for me (2019).

Versicherungskammer Bayern

jira.permission.createclone.denied is the only key, that doesn't produce a stacktrace, other keys are working but with error in the log file.
You dont need a property value, the value for Jira is the last word in the key after the last point, implizit value is denied
key: jira.permission.createclone.denied
value: none

Sayan Kaiser

Hi Guys,

I am able to restrict cloning for all users, but I need to unrestrict for some groups. How will I be able to do that ?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-administration

permission

clone