The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to configure JIRA's Clone functionality?

Hisamitsu Koga
Contributor
April 3, 2017

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?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Sam Hall
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 3, 2017

Hi Hisamitsu,

I believe the only things you can configure for clone functionality are:

  • The link type name given to the link created between original and cloned issues
  • The prefix added to the cloned issue summary (e.g. 'CLONE - ').

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".

Sam Hall
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 3, 2017

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

Hisamitsu Koga
Contributor
April 3, 2017

Hi Sam,

 

Thank you for your prompt reply. Understood.

Thuy-Van Watts
May 17, 2019

Sam,

does that post function happen all the time?  Even when you're creating a new ticket and have given it an assignee?

Thanks!

James Sims
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 9, 2019

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.. 

TAGS
AUG Leaders

Atlassian Community Events