Project avatar not showing up whatever it's set to

[Deleted user]

After migrating from server to cloud, none of my project avatars are working. They all show up as broken images regardless of whether it's a stock image or a custom uploaded one.

If I go to edit the project, this is what I see. If I click to select and choose an image, the correct image is displayed in the area below, however if I then click update and go back to edit the project I'm presented with the same broken image. This broken Image also appears in every other place it would show around the JIRA interface.

image2016-2-10 9:39:24.png

I have tried re-indexing. I have tried clearing my cache. I have tried an incognito window. I have tried another browser. Looks like something's broken to me.

Dev tools shows a 403 error;

image2016-2-10 10:21:32.png

[Samuel Costa]

Hello there!

After restoring your instance, make sure you have all the images to the avatars in this way:

$JIRA_HOME\data\avatars

After this, restart the service: "Atlassian JIRA" and your problem will be solved.

Any question, just call us.

Cheers!

[Rina Nir (AC)]

The same phenomena was seen from moving between two server instances (v 7.1.9).

Problem was solved by clearing caches (as mentioned below for cloud instance):

1) take JIRA down.

2) Cleaning plugin caches (see details https://jira.atlassian.com/browse/JRA-27314)

3) start JIRA

[David Vielhuber]

Same problem here when moving from cloud to server.

Is there a current solution to this problem or is this still a bug?

[Richard Henretta]

I am experiencing this same problem when moving from cloud to server. 

[Timothy]

This is something that you'll have to raise a support issue with Atlassian to fix. It should just be a path issue.

[Deleted user]

Thanks - I've sent off a support request about this.

[Kağan YEĞİN]

Hi; any idea or support answer,

i have same problem 

Thank you

[Deleted user]

@Kağan YEĞİN I sent a support request - I'm not sure if I can link to it as it's on my personal account, but try anyway: https://support.atlassian.com/servicedesk/agent/JST/issue/JST-182033 It was fixed promptly. I'd advise you to send a support request yourself. This is the info I got back from support;

Thanks for writing in. It seems to be a caching issue. I noticed that the instance was not usable at the time so I took the opportunity to clear the plugin cache.

[Kağan YEĞİN]

Thank you for answer 

good day

[Karl Bennett]

Same issue here. Just one of many issues I have had to deal with when trying to migrate from server to cloud.