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
Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.