Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

No longer can access attachments when migrating to JIRA Cloud from JIRA server


Previous environment (upgraded JIRA nonproduction DB Atlassian Jira Project Management Software (v7.13.8#713008-sha1:1606a5c, Windows)), imported attachments as zipped data/attachments, Firefox 69.0.1 bit): 

works fine:



New environment (JIRA Atlassian cloud, Firefox 69.0.1 64 bit):

"Ouch! We can't load the image. /secure/attachment/16702/catalogslist-popover.PNG"

When attempting to access the URI directly (ditto Firefox):

"The image cannot be displayed because it contains errors"

There are several such issues reported on Atlassian Community, but none quite fits.


Would love to get this solved, as our devs need a working JIRA in order to continue. Thanks!

1 answer

0 votes

Hello Eugen,

Thanks for reaching out to Community for your errors after migration from Server to Cloud. While looking further into your issues we found you created a support request for this. We agree that this was the most appropriate path and would suggest you continue to work with support to have your issue addressed.

We do ask that once you have a resolution to the issue to share with the rest of the Community so others may learn from your migration issues.

Stephen Sifers

Hi Stephen -- my support ticket was promptly resolved by Atlassian support via submitting my attachment archive, which required a scripted renaming of the entire file tree in order to be importable (all done by support).

For whatever reason my (following the documented steps) upgrade path from a very old JIRA instance did not pick up that problem and fixed it automatically.

Like Stephen Sifers likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events