Session Timeout during CSV Import

[Stuart Zahn]

CSV Import wizard times out after 20-30 minutes during import of 1,000 issues with attachments. This is a problem because I need to view the import logs to determine if there were any errors.

Is there a way to prevent a timeout? Can the import wizard keep a connection to indicate progress for several hours? Is there another way to view the import logs to determine success of import in case of a timeout?

[Kimberly Deal _Columbus ACE_]

@Stuart Zahn

You might want to take a look at this KB article about large imports.  It seems that if your import is over 1GB there is recommendations from Atlassian about doing it in smaller sections, when importing into Jira Cloud.

https://confluence.atlassian.com/cloudkb/how-to-import-only-part-of-a-jira-export-into-jira-cloud-859461966.html

Specifically this section of the article.

Split your attachments import to avoid timeouts

If the attachments directory you're trying to import is larger than 1GB, you should consider splitting it to avoid timeout errors.

1. Unzip your exported .zip backup file
2. Create directories outside the backup directory called attachments-only-1, attachments-only-2, etc.
3. Drag or copy the data directory from the backup directory into the attachments-only-1 directory
4. Create a data directory in attachments-only-2, then create an attachments directory under it.
5. Move some of the project folders from attachments-only-1 to attachments-only-2

6. Zip (compress) both attachments-only directories
   Your compressed files should have the following structure:

   attachments-only-1.zip
   └─── data
         ├── attachments
         │         ├── ProjectKey
         │         │         └── 10000
         │         │  ├── IssueKey-1
         │         │  ├── IssueKey-2
         │         │        └── IssueKey-3
         │         ├── ProjectKey2
         └── avatars
   
   
   attachments-only-2.zip
   └─── data
         ├── attachments
                   ├── ProjectKey3
                   │         └── 30000
                   │  ├── IssueKey-1
                   │  ├── IssueKey-2
                   │        └── IssueKey-3
                   ├── ProjectKey4

7. In your Jira Cloud site, go to Settings in the Jira sidebar, System > Restore system to upload the first attachments file
8. Repeat with the remaining attachment import files.

[Mikael Sandberg]

Currently it is not possible to change the session timeout in Jira Cloud, in the KB I linked to you will find a request to have that option.

As a workaround you could try and import your issues in smaller chunks, that should help with the timeout issue.

[Stuart Zahn]

Importing 15,000 issues in smaller chunks than 1,000 at a time is a major pain and error prone.