Want to disable Clone Option for Jira Cloud

[Chetan Krishna Sai Naidu/Jira-Admin]

Want to disable Clone Option for Jira Cloud for users in a particular roles or at org level,  Please suggest.

Thanks In Advance.

[Bill Sheboy]

Hi @Chetan Krishna Sai Naidu/Jira-Admin 

Unfortunately that is not possible at this time. 

I understand why "disable cloning issues" is needed, as it can propagate poorly written, incorrect information to new issues, and does not encourage people to invest the time needed to create a new issue based on the new need.

There is a suggestion to add this feature, although it is quite old (from 2005).  You may vote for it or watch it to see any progress. https://jira.atlassian.com/browse/JRACLOUD-8497  It does note an elaborate work-around by changing workflow, and that obviously does not scale well for an entire site with lots of Jira projects.

Kind regards,
Bill

[Charlie Misonne]

Hi @Chetan Krishna Sai Naidu/Jira-Admin 

That's not possible. Cloning is not a separate permission in Jira. All you can do is restrict the creation of issues (at the project level)

May I ask why you want to do this?

Cloning is not more than creating a new issue with the same values as the original issue. Users would still be able to clone issue manually by providing the field values themselves even if that button was not available.

[Marcos Rivoira]

Hi Charlie .. let me answer the question.

when you clone an issue, you must know that there is a lot of fields, that should be cleared or reseted if you don´t want to have bad information. 

Jira has the avility to be set or configured to use in many process or metodologies of work . 

In our case, there is some peoples that creates the issues, and then throught the workflow diffeerent role complete some fields, and for example, in any moment you may want to create or publish a relase, and you can set Fix Versiones field in that momento. so when you clone an issue, you should clear the Fix Versions field if it was completed and that persson ro role, does not care about that. .

Component is other field that sometimes must be changed.

So, if Jira it is so flexible to adapt a lot of metodologies, i don see any problem if you allow to disable for all the clone link, or if you can set a permission to that action.  

[Charlie Misonne]

Hi Marcos,

Ok thanks for elaborating. I understand you want to avoid users to clone issues and leave some bad data behind.

Like @Bill Sheboy said in his comment it could be done by adapting the individual workflows as described in the workaround of https://jira.atlassian.com/browse/JRACLOUD-8497. But it is not ideal indeed if you have many workflows.

[Marcos Rivoira]

Hi Charlie .. thanks for understand.. 

I read about the workaround, but i think should be an easiest and appropriate way.

I dont know about how long is the time between "Future Consideration" and the "In Progress" status, but we are going to wait for the functionality!. 

Regards,

[Charlie Misonne]

I don't want to disappoint you but Atassian's feature request are not known to be resolved quickly (if ever resolved at all) :-)

This specific request is from 2005...

In other words: don't count on an implementation any time soon.

[Marcos Rivoira]

Hi Charlie.. i Know... Atlassian does not stand out fot meeting needs
of customers or users. There is a lot of very old suggestions or needs with a lot of votes and Altassian seems to ignore all them even if they make senses or appears to be useful.