Unable to complete bulk upload into jira from csv file

[Ifeanyi Onyeukwu]

error: status:1 Failed to load resource: the server responded with a status of 504 ()

[Paul Glantschnig _Appfire_]

@Ifeanyi Onyeukwu, welcome to the community.

A 504 is a gateway timeout: the server didn't finish the request in time. With CSV import that usually points to the size of the file or temporary load, not your data itself. A few things to try, roughly in order:

1. Check what already imported first. Before retrying, open the target space and see whether some work items were created. Re-running a partially completed import is the easiest way to end up with duplicates.

2. Split the file into smaller batches. Import a few hundred rows at a time rather than the whole file. Oversized imports are the most common 504 trigger, and smaller batches almost always get through.

3. Confirm the file encoding. As @Rudy Holtkamp noted, save the file as UTF-8 (not UTF-8 with BOM). In Notepad++: Encoding menu, select UTF-8, then save.

4. Try the legacy importer. If your import screen offers a "Switch to the old experience" link, the older importer is often more forgiving with larger files.

5. Make sure all configuration already exists. The importer into an existing space can't create new statuses, work types, custom fields, or field options on the fly. If your CSV references any that don't already exist in the project, the import fails. Add them first, then re-import.

6. Retry off-peak, then escalate if needed. If even a small batch still 504s, capture the date/time and request ID and raise it with Atlassian Support, since a timeout on a small file points to something server-side.

Hope that gets the import through.

BR, Paul

[Paul Glantschnig _Appfire_]

@Ifeanyi Onyeukwu one more option, depending on what the upload is for.

If you're mostly updating or enriching issues (filling in fields across a batch) rather than creating brand-new ones, you can skip the importer entirely. If you're open to solutions from the Atlassian Marketplace, JXL for Jira is a spreadsheet-style view of your issues.

You open your data in Excel or Google Sheets and copy/paste columns straight onto the matching issues, the same way you'd paste between two spreadsheets. There's no import job to time out.

To be clear, this isn't a drop-in replacement for first-time creation of a few hundred new issues from a file; the native CSV importer (in smaller batches) is still the most direct tool for that. JXL helps most once the issues exist, when you need to populate or correct fields without re-importing.

Disclosure: I work for the team that builds JXL.

Cheers, Paul

[Rudy Holtkamp]

Hi @Ifeanyi Onyeukwu ,

What I often see is that users export data from Excel to csv. If you do that than the encoding of the csv is with UTF-8 BOM (=Byte Order Mark). The import accepts UTF-8, not UTF-8 BOM.

With a tool like Notepad++ you can easily change it to UTF-8:

• Open the csv with Notepad++
• Go to the Encoding menu 
• Select UTF-8
• Save the file

[Trudy Claspill]

Hello @Ifeanyi Onyeukwu 

Welcome to the Atlassian.

At what point in the process did you get this error?

Did you check the destination Space to see in any of the work items were created?

Have you refreshed the page when the error displayed? 

Have you retried the process from the first step?