Attachment Broken when Importing from Jira Cloud to another Jira Cloud

[Hilmi Muktitama]

Hi everyone,

I recently tried to import a list of issues (that were previously exported from a Jira Project) using CSV Importer in Jira Import Wizard. When the process was completed, I noticed that all attachments were broken. 

Based on this article 
https://confluence.atlassian.com/cloudkb/importing-attachments-into-jira-cloud-using-csv-external-system-importer-966669960.html
the issues happened due to the attachments requiring some sort of authentication to access.

I've tried to do the exact same things (adding the credentials, email:API_token), but every time I did the import process, I've always received 

An exception occurred dealing with attachment

And then I also tried to hit the URL:

https://email:API_token@domain.net/attachment/content/13421

 in my browser, but it always show:

"errorMessages":["You do not have permission to view attachment with id: 13421"],"errors":{}}

The tricky part is I also tried to hit the exact same URL in my Postman, and it works!
So that eliminate a probability that my URL is wrong.

Please, I need everyone's insight about this case. Thank you!

[Alex Ortiz]

I see, yeah my solution was because I understood your question as moving from cloud to cloud.

Since you really want is to simply backup a project let me offer up a couple more suggestions.

First, the importing of the attachments is probably one of the hardest, most confusing things to do in an import.  I've done 100's of imports and I try to avoid dealing with attachments whenever possible.  It's not impossible though, I've managed to do it once, but the secret is in that api string you need to add to your attachment URL.

With that said, do you know if you are in Jira Premium?  Jira Premium users can simply archive their projects so that you don't have to delete anything (but they still hide).

Have you considered updating the permission scheme on the unused project so that only site admins can access (or maybe just a single user like you).  This will make it look like the project has been deleted, but it's still there, preserved should anyone need it later.

And finally, have you looked at more advanced solutions like Rewind's Jira Cloud Backups and restore capabilities (I'm sponsored by them for full transparency).  For a small fee, they'll take care of the backup and the restoration with a couple of clicks.

I'll try to play around with importing attachments as I feel it is something I need to understand better.  I'll let you know if I find out how to do it successfully.  

[Hilmi Muktitama]

Hi Alex,

Thanks (again) for replying.

Your first suggestion is the only one that seems doable for my case. I would love to hear more details about that API string you've mentioned.

This whole backup plan started due to my limited Jira storage, which is almost at maximum. The rest of your suggestions are good ideas, and they are already on my last resort plans. But for now, I'm still looking for alternatives without the need to spend anything.

[Alex Ortiz]

Hello Hilmi,

Have you tried doing a cloud to cloud migration?  I find that this is super beneficial and usually comes with less headaches.

https://support.atlassian.com/migration/docs/perform-a-cloud-to-cloud-migration-for-jira/

[Hilmi Muktitama]

Hi Alex,

Thanks for the suggestion. I've read your article, and unfortunately, that method was an overkill for my goals. 

My simple goals are:
I want to delete an unused Project(s). Still, I want to create a backup(s) just to be safe -> The approach that I chose is to manually export all of the issues on that project before I delete them and store the CSV in a separate place -> When I simulate the restore/import process, I found the problems above. 

Either I found the solution to fix the attachments issue, or I need to find another way to safely backup a Project....