nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Unassigned" user avatar missing in JIRA Cloud instance

Kyle Fritz

The avatar for the "Unassigned" user is missing and replaced by a broken link/image. See the screenshot.

There is a similar question about how this happens in JIRA server. Do I need to access some local artifact to troubleshoot this in Cloud?

Thanks!

Edit: I was referred to an existing bug tracking this issue. https://jira.atlassian.com/browse/JRACLOUD-74059. Please let them know it's affecting your teams if you get the chance.

Accepted answers

All comments

Chris Duvall

I also have the same issue.

Umair Khalid_e46oe8

same

Ian Wayne

Same here.

MD_5382aj

Experiencing the same issue for the last 12 hrs...

Manuel Venegas_dqw1g9

Same over here. Looks like a global thing.

unknown

Same here. Any ideas how to fix it?

Olga_8fm2gi

Same here

Marcelo Oliveira_5iszdn

I use the Jira cloud hosted and I have the same issue

Derek Hansell

Same problem here.

Brian Pfister_sho1gn

Here too

Tilo Baller

Same here. Image address is: https://avatar-cdn.atlassian.com/default?size=24&s=24

Alex Wack

Chiming in to report the same issue

Mark Ahnell

Same here, it's trying to hit https://avatar-cdn.atlassian.com/default?size=24&s=24

Eddie_mpy1zs

Same.

Marius Kurseth_aascyg

Geez, not fixed yet... just raised a ticket about it.

Ben Whitlow

I just commented on the official ticket.

Basically the old avatar management uses a CNAME to point to a destination that no longer functions. The new avatar management url actually already has the default icon.

Failing URL: https://avatar-cdn.atlassian.com/default?size=24&s=24

(CNAME points to dvez5bs0hjtmq.cloudfront.net)

Working URL: https://avatar-management--avatars.us-west-2.prod.public.atl-paas.net/default?size=24&s=24

(CNAME points to dbx4mvc16djf5.cloudfront.net)

Ben Whitlow

I just commented on the official ticket.

Basically the old avatar management uses a CNAME to point to a destination that no longer functions. The new avatar management url actually already has the default icon.