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.
Please find below screenshots for your reference.
Below is result screenshot whenever user tries to clone the issue.
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
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