It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to remove the prefix "Clone" when cloning Issues and Subtasks?

Objective - To elmiinate the "Clone" prefix from each Issue and Sub-Task when cloning an issue. For us, the prefix is unnecessary and complicates the cloning process.

I've seen mention of plug-ins for hosted installs, but nothing about how to modify the Clone settings in Jira on demand.

8 answers

2 accepted

5 votes
Answer accepted

Hey mates, Advanced Settings option is now available in JIRA Cloud! You can customise your own Clone prefix now.

  1. Go to Administration > System
  2. In General Configurations, choose Advanced Settings on the top-right corner
  3. Edit your option on jira.clone.prefix key



Does this impact the whole JIRA Agile instance (for a copy that has hundreds of projects) or can it be configured for each project?

This is applying to all projects. We don't have the feature to customise the prefix for each project at the moment.



2 votes
Answer accepted

Thsi is configured by an advanced setting but unfortunately that cannot be modified in onDemand. You might ant to check with Support!

I was afraid that was the answer I'd get....thanks Jobin.

I just don't see the utility in adding the Clone creates a lot of unnecessary work for us.

Do I need a differnt user account for the Support section? I tried adding a support request, but it keeps prompting me to login and my credentials are not working.

Any advice to actually get in contact w/ support is appreciated.


If you open a support case we can remove this from the advanced settings. Open a case from

All the best.

1 vote


Dave here at Atlassian Support; Unfortunately this is a restricted function in OnDemand and these are not something Support can generally change for you. This is due to a couple things; these are restricted for a reason and should not be changed without good (critical/blocker) reason, plus any change we make to an advanced setting could be overwritten during any of our weekly updates and we will have no way of notifying customers of this change or provide any long-term maintenance of these settings.

Hopefully you can understand our process here, and if these are important to you I would suggest filing a feature request so our developers/PMs can take this into consideration.



Hi Jason,

You'll need to create an account at and raise a ticket. Once you've done that if you link the ticket here I'll hop on it right away and get that taken care of for you :)




We are also annoyed by this "CLONE" Prefix... we are on OnDemand... can some one suggest some good way/shortcut to get rid of it? It will be really helpful, currently everytime after cloning we need to keep removing it.

Thanks in Advance



I can totally relate.....I'm not sure why this "feature" exists in the first place, but removing CLONE by hand is a real pain. Luckily the Atlassian support team can modify things on the server (if you're using the hosted version like I am) to eliminate CLONE for you. Once I posted the ticket, they got back to me and resolved the issue within a day.

Here's the llink to create your own ticket:

Good luck!


I was hoping to set up a TEMPLATE project where I can build repeating tasks/subtasks and just clone them as needed but it adds "clone" not only to the task bu all of the sub-tasks. Tacky.

I think writing an app that hits the API might be the only method for OnDemand. You could cycle through every open ticket and look for "Clone -" in the title and edit the title programatically.



Open a ticket at and the Atlassian team will modify your instance to remove the unnecessary CLONE from your templates.

Good luck!


https://support.atlassian.comis the site, jira.atlassian.comis the public facing bug tracker and is not monitored by support.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published Apr 09, 2019 in Portfolio for Jira

Portfolio for Jira 3.0 is here!

The wait is over... Portfolio for Jira Server and Data Center 3.0 is now officially here! Platform releases offer Atlassian an opportunity to shift our strategy, make bold predictions about t...

1,372 views 14 26
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you