Remove 'Clone' from all the bulk clone items without JQL

[Sian Snook]

How to I remove clone from all the clone item. Is it possible within Bulk change? i'll have to change 100+ singularly :( 

[Luka Hummel - codefortynine · Accepted solution]

Hi @Sian Snook

If you want to avoid the "CLONE - " prefix in future and are willing to use a Marketplace app, our app Deep Clone for Jira can clone issues with custom prefixes or no prefix at all.

Deep Clone offers a range of powerful cloning features designed to save you time and effort, especially when managing large-scale Jira instances.

[Sian Snook]

Thanks for help much needed :) 

[Trudy Claspill · Accepted solution]

Hello @Sian Snook 

Adding to what the others have said, there is a System level setting that causes "CLONE - " to be automatically prepended to the Summary when an issue is cloned. Your Jira Product Administrators could change that setting so that the text is not prepended, but it will affect the entire system, and would take affect only on issues being created by cloning after that point. It doesn't help you clean up the existing issues.

An alternative for cleaning up the existing issues would be to use an Automation Rule to find the affected issues and trim the text from the Summary field. There are limitations on how many issues can be processed by an automation, though. How many issues need to be changed?

[Bill Sheboy · Accepted solution]

Hi @Sian Snook 

For a one-time adjustment, the approach suggested by @Shawn Doyle - ReleaseTEAM seems a good one.

For on-going removal of that prefix to cloned work items, you could use an automation rule to do this when work items are created.  I only recommend this approach as you appear to be on a Premium license level and so the extra rule executions needed may not impact your teams as much.

Kind regards,
Bill

[Shawn Doyle - ReleaseTEAM · Accepted solution]

Hi @Sian Snook 

I wouldn't use Bulk Change.  I'd export to CSV, remove the word clone from the subject using sed or search and replace in your favorite editor, then reimport back into Jira.

[Sian Snook]

users wont be able to use CSV. any other ideas :) 

[Shawn Doyle - ReleaseTEAM]

I wouldn't want users to use bulk change.  

My "other idea" would be to set up a company policy to encourage bribes to the Jira admin to make updates for you.  

Automation as @Bill Sheboy suggests would be a good approach after initial clean up.