how to clone issues with unassigned status

[Sachin Guttala]

when someone cloned the issue it should get the assignee as previous ticket, it should be unassigned 

[Clara Belin-Brosseau_Elements]

Hello @Sachin Guttala

If you're seeking for an easy way to clone an issue and keep it unassigned, you can try our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc).

You can check our guide here.

You can try the app for free during 30 days (and it stays free under 10 users).

Kind regards,

Clara

[Luka Hummel - codefortynine]

Hi @Sachin Guttala

If you are willing to use a third party app, our Deep Clone for Jira could help you. With the Field Editor feature, you can set field values while cloning. Including setting the Assignee to Unassigned.

[Trudy Claspill]

Hello @Sachin Guttala 

Which result do you want; the new issue to be unassigned or the new issue to have the same Assignee as the original issue?

[Sachin Guttala]

Hi Trudy, we need new issue should be  in unassigned state.

[Sachin Guttala]

Hi @Trudy Claspill can i get the workaround for the query please.

[Trudy Claspill]

Hello @Sachin Guttala 

If you are using the Clone Issue option from the actions menu in an issue it is not possible to configure which fields get copied.

One work around would be to use an Automation Rule to check for newly created issues and set the Assignee field on those to Unassigned. If you want to do that only if the issue was created by Cloning then you would need to add a condition to check if the new issue includes a "clones" link.

If you are Cloning an issue through an Automation Rule then within the Clone action you can set fields, and there you could set the Assignee field to Unassigned.