The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to update fields in existing Jira tickets with an Excel file?

Karyna Lysikova
February 10, 2025

Hi everyone,

I need to update specific fields in already existing Jira issues using an Excel file. The issues are identified by their issue keys, and I want to modify certain fields (e.g., status, assignee, custom fields, etc.).

Is there a way to achieve this using Jira’s built-in import functionality, or do I need an external app like ScriptRunner or another plugin?

If anyone has experience with this, I’d appreciate any guidance or best practices.

Thank you in advance!

Best regards,

Karyna

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

2 votes
Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 10, 2025

Hi @Karyna Lysikova , yes, this can be done natively. You simply perform a CSV import, and you need to ensure that you include the issue key in one of the columns. Any values included for other existing fields will be updated. If you plan on doing this regularly I recommend that you first test with a single issue until you get it working the way you want and save the import template so it can be reused.

Karyna Lysikova
February 10, 2025

Hello @Jack Brickey

thank you for your reply.

Could you please let me know if there are fields that are already filled in in existing tickets - will they be then with the new import overwritten? 

How should I do that correctly, so that I only update fields (or fill new fields using import file) that I have in my CSV import file?

Appreciate your help.

Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 10, 2025

Hi @Karyna Lysikova , basically whatever fields you include in your import will result in updating the field.

Example:

  • your header row = issue key, summary, custom field 1
  • you have three rows of data (three issues)
  • after import the three issues will be update including the Summary and the custom field 1 to match the CSV contents

if you dont want fields updated then don't include in the CSV file. What I recommend is to first create a JQL query and set you columns to represent the fields you will update. Export the query then massage the CSV to represent what you want updated then import.

Like Karyna Lysikova likes this
Karyna Lysikova
February 11, 2025

Hi @Jack Brickey

thank you. I will try it. Thank you for your help :)

Have a good day

Like Jack Brickey likes this
Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 11, 2025

Please let me know how it goes and if it all works out consider accepting the answer.

Paul Oliver
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 18, 2025

Hi @Jack Brickey 

Thanks for the explanation. I tried to do this however I can't find the "Issue key" (yes, I also tried writing the 2 workds; screenshot shows typing "key"); could this be a project setting issue? 

csv import test.png

Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 19, 2025

That is odd. Something may have changed but unclear what that would be. If I get some time today I will have a look.

deepakpat
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 31, 2025

Same here, I can not see Issue Key in the mapping field. Is there any solution to this?

When tried to proceed without Issue Key mapping (could map Issue ID though), it creates a new issue, does not update the existing issue.

0 votes
Hannes Obweger - JXL for Jira
Atlassian Partner
February 24, 2025

Hi @Karyna Lysikova,

I trust that you'll be able to resolve this using the CSV import as already suggested.

Just for future reference: If you're looking for a somewhat more interactive experience, and are open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on: JXL for Jira.

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 long list of advanced features, including support for inline bulk editing via copy/paste. This works within JXL, but also between JXL and pretty much any other app, including Excel or Google Sheets.

This is how it looks in action:

copy-paste-excel-to-jxl-assignee.gif

So what you can do is to open your CSV file in Excel, and simply copy/paste the values over. You just want to make sure that you paste into the correct set of issues, of course.

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

DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events