Importing CSV data without updating the summary on tickets

[IJ]

I want to do a bulk update to a custom field for a set of approx 900 tickets in JIRA service desk (server).

I have two columns in my CSV - "Issue Key" and the custom field.

I attempted to import but it seems I must include "Summary". I put a value in this field for each ticket (just some random text) but this overwrote the summary for each of my tickets.  In order to get this to work I have to export the tickets from JIRA into excel first, including the Summary, add the custom field values and then import, so the summary value being updated was the same as the value already on the ticket.

Is there a way of importing where I can have the summary field not updated?

I'm sure there is a simple way to do this but I couldn't seem to find it.

[François Dumas · Accepted solution]

This is a known limitation and a suggestion has been logged about it in the support system:

https://jira.atlassian.com/browse/JRASERVER-69222.

As mentioned in one of the comments, the trick is to include an empty "Summary" column in your CSV and map it to the Summary field. 

That way, the import will succeed, the Summary will remain unchanged on your issues but the other fields included in your CSV will get updated, giving the desired result.

[Thierry BLOCH]

I love the trick!  Thank you

[Roman Kersky]

HI, Sorry but .... may be create script and update the fields using the REST API

[Elvis McNeely]

This actually does not work for me. I'm using Jira Cloud...

See screenshots below.

First I tried without mapping the summary. I'm warned the summary field is required. Ok, let's adding an empty summary field. See next screenshot.

I went back to the CSV file and added a new column called Empty Summary. Notice the Issue ID is also set. Also notice the other fields I'm mapping...

Upon running the validator, an error is thrown saying the Summary field can't be empty. What gives?

If I map the regular summary column (which has the original summary value from export), upon importing I get duplicate issues, even though I'm providing the issue-id and summary fields. The update is not happening. There must be another require or reason for this.

Any help would be appreciated.

[Michiel Schuijer]

Just name the column "Empty Summary" in your CSV file "Summary", without the "empty" word in front and leave the column values empty. Did you try that?

That is the trick @François Dumas mentioned and you could try:

As mentioned in one of the comments, the trick is to include an empty "Summary" column in your CSV and map it to the Summary field. 

[Fdumas (external test)]

.

[François Dumas]

@Elvis McNeelyin order to update existing issues, you must map the "Issue Key" field, not the "Issue Id" as you have done, otherwise Jira will attempt to create new issues (and the Summary cannot be empty on new issues, which is why you're getting that error).

The proof that Jira is trying to create new issues is the error message in your second screenshot which displays:  "Issue can't be created due to error/s..."



So, to update existing issues:

• Map the "Issue Key" field,
• Map an empty "Summary" field as per my original answer
• Map any other field you wish to update and it should work fine! 😊

[Tomas Gustavsson]

If ju have a plugin called jira suite util or perhaps scriptrunner,  this should be an eaay task.

then you should get something looking as below

[IJ]

thanks for the feedback - but I want to try and accomplish this through the native JIRA CSV import.  I want to understand if just not updating the "Summary" field during import is possible?