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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Is there a way to disable cloning for Initiatives only? - some critical fields like cost / risk/ cutom backend identifiers / system generated fields are being copied over too; Many times users fail to update those. This causes data integrity issues. Either disabling the clone function for the issue type or ability to ignore certain fields when cloning by default will help. Please advise.
Hi @Nayana Geddam ,
You need to have separate workflow for Initiatives and for each status you need add below property in properties of status.
Property Key:jira.permission.create.clone.denied
Value:true
Please find below screenshots for your reference.
Below is result screenshot whenever user tries to clone the issue.
Thanks,
Avinash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.