Normally JIRA Clone function clones all contents including Assignee field data
to cloned ticket. Is it possible to configure JIRA's Clone function not to clone
original ticket's Assignee data to the cloned ticket (in this case, Assignee field data is "Unassigned")? If yes, how can we come true?
Hi Hisamitsu,
I believe the only things you can configure for clone functionality are:
Info about configuring these on JIRA Server is here: https://confluence.atlassian.com/adminjiraserver073/configuring-issue-cloning-861254006.html
There isn't functionality to exclude certain fields (like Assignee) from the cloning process, as far as I know.
A workaround you can do is add a post function to the 'Create' transition in your workflow. For this, you can use the "Update Issue Field" post function and set the assignee field to "Unassigned".
This will ensure all newly created issues (including cloned ones) get assignee set to "Unassigned".
Your other option is to search the Atlassian Marketplace for add-ons that enhance the clone functionality:
https://marketplace.atlassian.com/addons/top-selling?hosting=server&query=clone
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sam,
Thank you for your prompt reply. Understood.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sam,
does that post function happen all the time? Even when you're creating a new ticket and have given it an assignee?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thuy-Van Watts,
Unfortunately, yes. The function will happen any time a ticket is created (from scratch and clone) and will overwrite the field even if the user entered an assignee prior to submitting the ticket.
I, too, researched this a while back and found that most of the workarounds (most require add-ons/groovy) are pretty dirty hacks to recognize the Clone vs. New ticket.
If anyone has a clean and reliable workaround, please update. thanks..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.