Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,298,157
Community Members
 
Community Events
165
Community Groups

Disable Clone for an issue type (Initiatives)

Edited

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.

1 answer

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.

clone 1.pngclone 2.pngBelow is result screenshot whenever user tries to clone the issue.

clone result.png

Thanks,

Avinash 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

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...

159 views 1 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you