Only first 10 projects show custom project image

[Mike McNamara]

I have set custom project images for each project. After creating the 11th project I notice that the custom image does not appear in the overall Project List - it shows the standard default image. The project itself does show the proper image, but the "View Project List" page does not show the assigned custom image. This occurs whether I upload an image or if I choose from the supplied Atlassian images.

Self hosted server version 7.10

AS400 Sunset and SAP Stabilization projects have custom images but they do not appear in this overall project list view,

[Andy Heinzer · Accepted solution]

I was able to partially recreate this problem, but it didn't take me creating 10+ projects to do this.   I was able to recreate this behavior in only 5 projects in my setup.  I started by giving each of my projects a custom avatar (uploaded image).   By the fifth project I noticed this problem.  But I then continued to create at least 11 projects in case there was a specific number limitation here.

I found that while each project in the project settings was reflecting the correct avatar, for some reason the view projects list was still holding on to the old default avatar.   I refreshed my browser, and this did not correct the issue.  I was about to see if restarting Jira would fix this, but then I did hard refresh in my browser (Hold Shift while clicking the refresh button).   In my version of Chrome I found that this immediately corrected the problem, and my project avatars were all correct.  The hard refresh will clear your browser cache and request the page again from Jira.

Can you try this and let me know if this helps?

Andy

[Mike McNamara]

Wow, yes, that did work! Held down shift key and pressed the page reload icon. Now the Project List view has the correct image icon for all projects. I attempted to edit the image on an existing project, and it did not update in the list view, but performing the shift-reload, it corrected that issue. 

So not sure if it is application or browser level issue, but this workaround does fix the problem. Thanks!