Disable Clone for an issue type (Initiatives)

NAYANA
Contributor
October 24, 2019

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

4 votes
Avinash Bhagawati {Appfire}
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 24, 2019

Hi @NAYANA ,

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