You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.