Update some fields in existing JIRA issues with CSV import without all fields in import?

Is it possible to update existing JIRA issues using a CSV import without all the data fields in the exisiting issues in the CSV and without having the existing fields overwritten if they're not specified? The documentation for 6.2 says:

(warning) Importing a CSV to update existing issues will reset columns to their default values if they are not specified in the CSV.

Here's the use case: I want to have a series of QA issues worked on internally that can be exported to XLS to show to a client. I want the client to add feedback to a column in the XLS corresponding to a client feedback field in the JIRA issues. I want to import that XLS via CSV back into the existing issues in JIRA, but without the other field data in the CSV because it will have changed over time in JIRA as the internal team works through the issues. I only want to add the client feedback by key and nothing else (and this feedback field would not be modified in the interim).

Is this possible? Thanks in advance!

4 answers

1 accepted

This widget could not be displayed.

You can write a script which will update only the required fields through JIRA REST API https://docs.atlassian.com/jira/REST/latest/#d2e3550, using the CSV file to get the values for the feedback

This widget could not be displayed.

JIRA Command Line Interface has runFromCsv that will construct actions based on CSV data. Specifically, you can run updateIssue.

This widget could not be displayed.

Thank you both!

This widget could not be displayed.

why is it you cannot update a single field for a bunch of issues when there is a unique identifier (key), why is it you need to provide every field including the ones you dont want updated? when, if using an sql database with management studio i could simply update a single column (field)?

I understand this is not exactly the same but i dont understand why if the fields are not present in the csv update that the issue retains its current values for those fields?

Sam Hall Community Champion Apr 12, 2017

This works for me. Perhaps the import functionality has been improved since this original 2014 thread.

I do CSV import with 3 columns:

  • Issue Key (mapped to issue key in JIRA, to ensure issues are updated rather than created as new)
  • Summary (required by the import process)
  • Field I want to update

Importing this using Admin > External System Import results in only that one field (and the Summary, if changed) being updated. Fields not included in the import file are unaffacted.


Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

130 views 2 0
Join discussion

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