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".
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs