Disable Clone for an issue type (Initiatives) Edited

[Nayana Geddam]

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.

[Avinash Bhagawati _Appfire_]

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