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?
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".
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..
Introducing Jira Cloud for Excel Here at the product integrations team at Atlassian, we are thrilled to announce the new Jira Cloud for Excel add-in! This add-in lets you export Jira data directly ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events