how to configure fields when a ticket gets cloned

[Varsha Mungale]

I have some custom fields on the "Bug" type of ticket. When people clone a Bug ticket all these custom fields are getting cloned and causing confusion.
I want a way to either 
1. restrict Bug type of tickets from "clone" action 
OR 
2. Configure these custom fields so that these do not get the values from the original ticket. 

[Hans Polder _Devoteam_]

Hey @Varsha Mungale ,

It's not possible to restrict cloning for specific issue types. Perhaps it would be with (paid) addons. But, I can suggest a workaround that should work:

You could create an Automation Rule that triggers when the issue is created, and checks if the summary starts with 'CLONE - '. If that is true, you can edit multiple fields to be set to another value, or be emptied.

This is not air tight, as people can of course change the Summary of a ticket during the clone action.

You could also consider adding conditions based on the Issue Link present. This should be better since this is a system default issue linking that should happen by default when cloning an issue. See suggestion below:

Please let me know if this helps!

[Luka Hummel - codefortynine]

Hi @Varsha Mungale

If you want to configure fields when cloning Jira tickets, our app Deep Clone for Jira offers a powerful solution.

With Deep Clone for Jira, you can customize and automate field configuration during the cloning process. Here are some key features:

• Field Editing: You can use the Field Editor to automatically modify (or clear) fields in cloned issues. This includes setting default values or adjusting specific fields as needed.
• Jira Expressions: Advanced users can utilize Jira Expressions to apply dynamic field configurations during the cloning process.
• Presets: If you frequently clone issues with the same field configurations, you can create presets to streamline the process.
• Post-Function Integration: Integrate cloning into Jira workflows with post functions for automated field adjustments based on workflow transitions.

[Varsha Mungale]

Hi Luka 
Thanks for the response. I am trying to get it done without additional plugins. 

[Varsha Mungale]

Hi Hans, 
i was using the 2nd option that you have suggested and was just deleting the cloned ticket. 
Now i have tried your idea about setting the fields to some values -  am currently struggling with json syntax errors since my fields are single select list and multi-select lists. 
But the idea works 
Thanks

[Hans Polder _Devoteam_]

Hey,

I don't think you need to use JSON, you could simply add the fields that you want to be emptied, and leave them empty. This should clear out the fields, even select lists (the TEST custom field in the screenshot below is in fact a single-select list field)

Otherwise, if I'm missing something, please share more details so we can check what's going wrong. I'm not a big expert on json stuff, but we can give it a try :)

[Varsha Mungale]

Ohk.. Somehow leaving it blank did not work. Assigning a dummy value, say, 0 worked. Will give it a try