nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to bulk edit the summary field

Shiva Dainak

I need to add an additional common text ( heading of the parent issue) to all the subtasks.

I tried doing this with bulk edit, but bulk editing of 'summary' field is not allowed in JIRA.

I think JIRA should allow the bulk edit option for summary field ( only - 'add to existing text').

Accepted answers

Ste Wright

Hi @Shiva Dainak

If you're a Jira Admin, you can do this using CSV Import.

This is how I'd do it:

Go to Filters > Advanced Issue Search
Search for all sub-tasks which need to be modified
Make sure Summary is one of the visible columns, then press Export > Export Excel CSV (current fields)
Modify the Summaries in Excel in bulk
Ensure the Issue Key remains on the CSV file, along with the Summary, then re-save the file.
Next, as a Jira Admin go to Settings > System > External System Import
Select CSV, and follow the steps to upload your file. Ensure when mapping the fields you map "Key" to "Issue Key" so the importer updates the existing issues, rather than creating new ones

For more information on updating issues via CSV import, see this page - specifically the section Updating existing issues

Ste

All comments

Ste Wright

Hi @Shiva Dainak

If you're a Jira Admin, you can do this using CSV Import.

This is how I'd do it:

Go to Filters > Advanced Issue Search
Search for all sub-tasks which need to be modified
Make sure Summary is one of the visible columns, then press Export > Export Excel CSV (current fields)
Modify the Summaries in Excel in bulk
Ensure the Issue Key remains on the CSV file, along with the Summary, then re-save the file.
Next, as a Jira Admin go to Settings > System > External System Import
Select CSV, and follow the steps to upload your file. Ensure when mapping the fields you map "Key" to "Issue Key" so the importer updates the existing issues, rather than creating new ones

For more information on updating issues via CSV import, see this page - specifically the section Updating existing issues

Ste

Marlene Kegel - codefortynine

Hi @Shiva Dainak and welcome to the community!

You can also use our Jira cloud app Advanced Bulk Edit for Jira to bulk edit the summary.

With our app you can:

Add text as a prefix
Add text as a suffix
Replace terms with other terms (e.g. replace "bunny" with "rabbit)

Don't hesitate to contact our support if you have questions or feedback about Advanced Bulk Edit for Jira.

כל זכות

I love you, @Ste Wright. This saved me a lot of time.

Ismoyo Eko Purwanto

hi @Ste Wright

I have an error when importing the data. I just want to bulk edit labels, so I just map : Summary (as required one), Issue Key and Labels.

Here is the screenshot of the error. Please advise. Thank you.

Kind Regards,
Moyo

Screen Shot 2022-01-23 at 21.10.49.png

VVor

If you have a ScriptRunner plugin, then you can create a Listener with it, which will do the job.
I did it this way:

created a new custom "text single line" field - Summary_hidden (without adding it to screens), with "Indexing" switched to Off
created a Custom Listener for Issue Created & Issue Updated events

The Listeners code do the job - when it is triggered it takes data from hidden field and put it into the system field, then do re-index. The Summary_hidden field is visible on the Bulk Edit page.

import com.atlassian.jira.event.issue.IssueEvent

import com.atlassian.jira.issue.IssueManager
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.event.type.EventDispatchOption

import com.atlassian.jira.issue.Issue 
import com.atlassian.jira.component.ComponentAccessor

import com.atlassian.jira.issue.index.IssueIndexingService
import com.atlassian.jira.util.ImportUtils

import com.atlassian.jira.issue.fields.CustomField

Issue issue = event.issue
IssueManager issueManager = ComponentAccessor.getIssueManager() 
def currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()
MutableIssue issueMutable = (MutableIssue) event.issue
final String CUSTOM_FIELD_ID_FOR_SUMMARY_HIDDEN = "customfield_11900"
def customFieldManager = ComponentAccessor.getCustomFieldManager()
def cf = customFieldManager.getCustomFieldObject(CUSTOM_FIELD_ID_FOR_SUMMARY_HIDDEN)

String summaryValue = issue.getSummary()
String summaryHiddenValue = issue.getCustomFieldValue(cf)

String eventTypeName

if (event instanceof IssueEvent)
{
Long eventTypeId = event.getEventTypeId();
def eventTypeManager = ComponentAccessor.getEventTypeManager() 
eventTypeName = eventTypeManager.getEventType(eventTypeId).getName()
//debug
//log.warn("SummaryChanger: eventTypeName=="+eventTypeName+" JRA_ID=="+event.issue.key)
//debug
}
else
{
return
}

def changeLog = event?.changeLog
def changeItems = changeLog.getRelated("ChildChangeItem")
Boolean IssueSummaryChanged = changeItems?.find{ it.field == "summary"}
Boolean IssueSummaryHiddenChanged = changeItems?.find{ it.field == "Summary_Hidden"}

//debug
//changeItems.each{log.warn("SummaryChanger: Items: "+it)}
//debug

Boolean needIssueReindex = false

if ((eventTypeName == "Issue Updated" && IssueSummaryChanged) || (eventTypeName == "Issue Created")) // filling the hidden field. if you need it.
{
issueMutable.setCustomFieldValue(cf,summaryValue) // копируем новое summary в скрытое поле
issueManager.updateIssue(currentUser, issueMutable, EventDispatchOption.DO_NOT_DISPATCH, false)
//needIssueReindex = true
}
else if (eventTypeName == "Issue Updated" && IssueSummaryHiddenChanged) // summary_hidden updated via bulk update (field is not on any screens, so bulk update is the only possibility to change it)
{
issueMutable.setSummary(summaryHiddenValue)
issueManager.updateIssue(currentUser, issueMutable, EventDispatchOption.DO_NOT_DISPATCH, false) 
needIssueReindex = true
}

if (needIssueReindex)
{
def issueIndexingService = ComponentAccessor.getComponent(IssueIndexingService)
Boolean wasIndexing = ImportUtils.isIndexIssues()
ImportUtils.setIndexIssues(true)
//debug 
// log.warn("SummaryChanger: Reindex issue ${issue.key} ${issue.id}")
//debug 
issueIndexingService.reIndex(issueManager.getIssueObject(issue.id))
ImportUtils.setIndexIssues(wasIndexing)
}

I'm a newbie to the Java/Groovy, so, please do not blame me

Ste Wright

Hi Ismoyo,

Did you rectify this issue?

Ste

Laura Anderson

@Ste Wright Hi Stephen - you there?

Georgi Tunev_mi76fb

You probably don't need this anymore, but I had this problem the last couple of days and I managed to solve it via custom automation.

Important: make sure to use the "Add value to the audit log" action in order to make sure that your code will work as expected. The changes that you will make are irreversible.

My case - I am migrating from Zendesk to JSM and I wanted to add the original Zendesk ID to the summary of the migrated Jira ticket. Here is what I did:

I added the Zendesk ID as a custom field in the migrated ticket. I also got the reference to that custom field.
I created an automation with a Scheduled trigger and a JQL search that would ensure that I will be working only with the tickets in that particular project (e.g. my JQL was something like "project = TSM").

Important: The reason why I used a Scheduled trigger is tht it has a "Run rule" option that allows me to run it immediately after creating it. Do not forget to disable the automation after that
I added a condition where I make sure that the summary does not already contain such ID (e.g. Issue Field Condition > Summary / does not contain / "ZD id" )
Finally I added the action that would change the Summary field (e.g. Edit Issue / choose to set the Summary field) and used the following as my replacement code: {{issue.summary}} (Zendesk ID: {{issue.customfield_10120}})

IMPORTANT: use the "Add value to the audit log" action first, to make sure that your replacement string will work correctly. In my case I used to log "Key: {{issue.key}}; ZD id: {{issue.customfield_10120}}" and continued only when I saw in the audit log that it gets the field's value correctly, i.e. the result was something like "Key: TSM-42; ZD id: 1272"
Once the rule was published, I used the "Run rule" option.
I disabled the automation rule after confirming that the renaming operation went successfully.

Monica Brazelton

I have a way of doing this that I think is even easier than the solutions above. I'm on Jira Cloud, so this might not work on Jira Server.

Save all the issues where you want to add to the summary in a filter
Create an automation rule
- Trigger: Scheduled trigger, you can do every 15 minutes but the interval doesn't really matter. Have the trigger search for and only act on issues that are in the filter.
- Action: Edit issue fields, if you want to add to the summary use the smart value {{issue.summary}} + the text you want to add to the summary
Publish and enable the rule
Run the rule (there is a manual trigger next to where you enable/disable the rule)
The rule will act on the issues saved in your filter
Disable the rule

Sriharsha_77yenc

By far the only easiest solution. Thank you so much

Monica Brazelton

Glad this is helpful @Sriharsha , please vote for my solution if you haven't already

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

atl-orange