This would be a great wil for QOL

This is still relevant and needed  - changing clone names manually across large projects is really annoying and time consuming!

I despartely need this feature also.,

Why is this suggestion closed? Will this be done or not? I would like to vote for this required feature, too.

Need this as a feature as well please ASAP

Not via CSV but built-into Jira and only for your jira's somehow perhaps. Because org's won't be keen on enabling it for just Jira Admins, but an ability to do this but only to your OWN JIRA's (i.e. reporter=<you>) will be fine

My use-case for requiring this feature is that we have a template Epic which is cloned for every handover of an application into my support team. I need to bulk edit the summary of every issue that says, for example, "Knowledge Transfer of automated testing for <<Business Application>>" to replace <<Business Application>> with the actual name. We have a large number of issues in this template Epic so manually changing them is a real inconvenience.

How many customers do you now have asking for this feature? Why is it not important to you when it is important to us? @dmayer @Dadve Meyer

 i need this too.

This is an incredibly short sighted response from Atlassian on this request - you could use the SAME argument about all fields that are available within Bulk Edit feature.  Bulk change is not there JUST to make all the fields the same - sometimes you might want to append or remove a text string 

Please reconsider re-opening this request.

My workaround uses ScriptRunner Listener and additional hidden custom field to achieve this.

My code can be found in community answer here

You can add some code to implement the functionality for replace/add prefix/suffix.

@Dave Meyer, please look to consider this again, this does not seem like a difficult ask, and many use cases noted in the comments (and others I'm sure).  Thank you!

It's not often I need it, but there has been more than once where I wanted to bulk update a summary. It's frustrating that I can't. Jira is used in many ways and I need to do this at times. I agree with others...why would you actively prevent this?

I believe there is the capability to set whether the new ticket is marked with the clone prefix. https://community.atlassian.com/t5/Jira-Core-questions/How-can-I-disable-clone-sub-task-prefix/qaq-p/70118

There can be many reasons why you would want to keep the name the same.  One that I used often is when a ticket from one project spawns a ticket in another project.  I first clone the ticket, then move the cloned ticket to the other project.  Saves a lot of tedious typing.  Other times, you may want to clone a ticket and then modify the summary.  The clone prefix just makes more work. 

Why would you as a company that cares about its customers want to actively prevent it?

+1

> As every issue in JIRA is generally different from the previous one, I'm not sure why you would want to make all of the summaries the same

Why would you as a company that cares about its customers want to actively prevent it?

As every issue in JIRA is generally different from the previous one, I'm not sure why you would want to make all of the summaries the same.

Another example for where editing the summary is useful is when cloning an issue - say for a repeatable task in each iteration. If that task has sub-tasks and you choose to have them created, they all end up prefixed with "Clone -". Do it twice and you'll get "Clone - clone -".

As every issue in JIRA is generally different from the previous one, I'm not sure why you would want to make all of the summaries the same.

That is not true. I have the same job assigned to many people and I want to update the description of each job. Another example we have the same task created for many components and we want to bulk update the summary. Or the same subtask in many tasks. We can update almost any field, but not the most important ones.

I have 100+ test case designed for move and copy operations. I just need to replace "move" with "copy" which is easy in ALM however in Jira there is no option other than mannually edit one by one.

Please implement it.

Yes, we would also like the ability to change and replace Summary. Dave, I wanted to exactly the same thing. Export --> change then Import. Did that work for you? Were you able to map or override the rest of the fields?

I also would like the ability to "search and replace" across Summary fields. We bulk-import issues and periodically would like to "fix" a bunch of issues' Summaries.

As a work-around, I'm going to try exporting a list of issues to CSV, use a text editor to do the search-and-replace, and then do a bulk import to update the issues. Not elegant, but it should work?

Dave,

My company uses Jira for many purposes, including Asset Management. I would like to Bulk Edit 48 Jira tasks to change the summary. Imagine changing 48 tickets (assets) to a more specific description of the hardware asset.

Regards,

Steve

That's too bad. Sometimes you may want to clone tickets and just for the fact that you want to get rid of the CLONE or CLONE-CLONE or CLONE-CLONE-CLONE prefix in the summary this would be a nice feature to have. Why have an automation tool when you still have to spend unnecessary time typing? It would seem that this would be an easy enhancement.

Hi everyone,

Thank you for your feedback. This request is not going to be a priority for the JIRA development team for the foreseeable future.

Please contact me if you have any questions.

Dave Meyer
JIRA Product Manager

In a different Jira installation (I think in Jira Cloud) I have seen the possibility was there. I am quite sure, the functionality is somewhere and somehow available.

Josh,

I think us paying customers can be the judge of what fields we'd like to be able to bulk edit. Can you re-open this and implement bulk-editing of summaries, please and thank you.

Ron

The requirement should be "allow find replace across issues" or "allow substring change on bulk edit".

The idea to me is that I just put in a bunch of tasks that include a certain term like "Module A - do X", "Module A - do Y" and I want to change "Module A" to "Module B" wherever it occurs. Perhaps there is some other way to do this?

Hi Elke,

As every issue in JIRA is generally different from the previous one, I'm not sure why you would want to make all of the summaries the same.

We will not be implementing this feature in JIRA because of the above reason.

Regards
Josh Devenny
JIRA Product Management