CSV Import Files For Editing
Asked by Ryan Cannata:

Is there a way to edit current stories in Jira by using a custom field (Claim Number) vs Issue Key when using the CSV import option?


Answers:
author: Hans Polder
body: Yes :) See more answers and context here: [https://community.atlassian.com/t5/Jira-questions/Whether-Jira-supports-updating-existing-issues-using-CSV-import/qaq-p/1008434#:\~:text=Yes%2C%20you%20can%20update%20any,%2FExternal%20system%20Import%2FCSV](https://community.atlassian.com/t5/Jira-questions/Whether-Jira-supports-updating-existing-issues-using-CSV-import/qaq-p/1008434#:~:text=Yes%2C%20you%20can%20update%20any,%2FExternal%20system%20Import%2FCSV).

comments: author: Ryan Cannata
body: It looks like this this link is stating you need to use Issue Key on your import file when updating items in Jira when using External System Import. I'm wondering if I can use a different field from the import file to link to a current story instead of Issue Key.


author: Hans Polder
body: No, it definitely needs to be the issue key. Why would that be a problem? If a certain change only applies to tickets with a certain value in a certain custom field, should you not filter those out, then export these tickets, and use the issue keys in question for the CSV import?

There are also several plugins out there in the Marketplace (which are often paid, by the way) that allow for much more customization/'bulk changes' in the UI, rather than having to do this via CSV file.


author: Hannes Obweger - JXL for Jira
body: Hi [@Ryan Cannata](/t5/user/viewprofilepage/user-id/4351876)

I understand that your looking for a CSV-import-based solution, but just as food for thought: If you're open to solutions from the Atlassian Marketplace, you might want to have a look at the app that my team and I are working on, [JXL for Jira](https://marketplace.atlassian.com/apps/1224710?hosting=cloud&tab=overview&utm_source=atlassian-community&utm_medium=referral&utm_content=2771744).

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you'd do in e.g. Excel or Google Sheets. It also comes with a range of advanced features, including the ability to inline bulk-edit your issues via copy/paste. This works within JXL, but also between JXL and pretty much any other app, including e.g. Excel.

This is how this looks in action:

![copy-paste-excel-to-jxl-assignee.gif](https://community.atlassian.com/t5/image/serverpage/image-id/339450iBF302FA00D14837D/image-size/large?v=v2&px=999 "copy-paste-excel-to-jxl-assignee.gif")

This is updating the assignee, but it works for any other field as well. As you can see, you don't need the issue key in your Excel/CSV file - you really just need to make sure to paste into the correct set of issues.

I should also add that JXL can do much more than the above: From support for configurable *issue hierarchies* , to *issue grouping* by any issue field(s), *sum-ups* , or *conditional formatting* .

Any questions just let me know,

Best,

Hannes

comments: author: Hans Polder
body: [@Hannes Obweger - JXL for Jira](/t5/user/viewprofilepage/user-id/4289506) haha, you're always hot on my tail! I love your enthusiasm :-)


Tags: cloud

jira-work-management-cloud