Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,462,954
Community Members
 
Community Events
176
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

Atlassian Community Events