While cloning , it autofills the assignee from previous ticket being cloned instead of unassigned .

[manoj kumar]

When cloning ticket from jira ,it auto fills the assignee from the ticket being cloned  so this ticket auto-assigned but the assignee hasn't  picket up the issue . So it has to be in unassigned status so that the available resource can. Easily pick it up and  work on it . Kindly help me with resolution for this question / share any document link for  post function  on clearing the asssignee field please?

[Marlene Kegel - codefortynine]

Welcome to the community, @manoj kumar.

I am Marlene from codefortynine.

If you're open to work with an app, you can try Deep Clone for Jira.

With our app you can unassign the issue while cloning. 

• Select the issue you want to clone
• Click Deep Clone in the issue action menu
• Configure you clone and set "assignee" to "unassigned" in the Deep Clone Field Editor

If you perform a clone with these settings on a regular basis, you can create a "preset".

[Mohamed Benziane]

Hi,

welcome to the community

This is how cloning works, it copy some field from issue A to issue B. May be you can look at a post function that will clear the assignee field in the newly created issue.

[manoj kumar]

Can you share any document link for  post function  on clearing the asssignee field please?

[Mohamed Benziane]

Look at the "Optional post functions" section

https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/

[manoj kumar]

which transition should i select for cloning process.becaise I don't find  cloning stage in workflow.