Forums

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

JIRA CSV import - issue with uploading attachments

Elizabeth Jarvis June 7, 2019

Hi, I was wondering if anyone has ran into something similar to what I am seeing in a batch of imports:

I am trying to import through csv files from a JIRA Cloud instance to a JIRA Server instance (v.7.9).  The imports are going well and without any unexpected errors, except that the attachments are maxing out at 8 kb.  I am not receiving errors from the import about not being able to upload the files, but when I go to a ticket with an attachment that is larger than 8 kb, that attachment is corrupted (ones less than 8 kb open fine).  

I double checked our instances max allowed attachment size, and it is ~120 MB.  The max allowed attachment size from the originating instance is ~56 MB.  I also confirmed that the attachments are not corrupted in the originating instance.  

Does anyone know if there is something else that could be restricting the allowed size of an attachment file imported through a csv?

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 10, 2019

Hello Elizabeth,

After some time digging into similar cases and documentation to find any details about this problem, I think you are being impacted by the bug below:

Attachment problem after migrating from JIRA Cloud to Server

The bug above explains that:

  • The Problem happens because Cloud instance shows filesize-0 from the issue page.
  • Attachment affected by this problem will also shows filesize=0 in Cloud instance's fileattachment table.
  • Since the value of the filesize is saved as 0 in the database, the filesize will be saved as 0 in entites.xml generated for JIRA Server migration.

That been said, there are no customers feedback about the exact scenario you are facing, where only attachments larger than 8 kb cannot be imported.

With all that information in mind, I would recommend you to open a support ticket with our standard support so we can perform a deeper investigation in the logs and check if you are being impacted by the mentioned bug or anything else:

https://support.atlassian.com/contact/

Let me know if you still have any questions.

Suggest an answer

Log in or Sign up to answer