[Bug] Removing a profile picture on Jira doesn't take effect

[Isaac Chua]

After removing my profile picture using the profile feature on Jira, it still shows up throughout the Jira instance such as where the Backlog, Board, and so on are. This is a bug and should be fixed.

The current workaround is to go to id.atlassian.com, click on the "X" on the avatar, and save the profile. This would definitely remove the profile picture.

[Andy Heinzer]

Hi Isaac,

Thanks for detailing the problem here.   I was able to partially recreate this scenario in my own Jira Cloud site.  However when I removed my profile picture in my case, it actually did appear to be removed from the entire site.  That is, until I logged out and then logged back into my Cloud site. 

At that point the Cloud site appears to be synchronizing that user data with our Identity platform https://id.atlassian.com which in turn did replace the profile picture in my case.

I can respect your point of view that this is a bug, but in my view, I think this is actually a feature of the Identify platform and the way that Atlassian has setup this particular integration.  As such I see this as intended functionality of the site in this case and not exactly a bug.

That said, I would be interested to create a new feature request that would allow users or site admins to have the option on whether or not data like this (avatars, name, email, etc) should be synced to Cloud sites upon user login.  If implemented it would give the end user a bit more control over which user data is synchronized on login.

So far I have not found any other feature requests seeking this behavior, but I could see how this might be useful to users that exist in multiple Cloud sites that don't necessarily want to have the same avatar in every site but want the same login credentials.

[Isaac Chua]

It seems that your experience is different from mine — removing the profile picture in Jira Cloud did not take effect for me and my colleagues, regardless of logging out and in. That said, I do not have an opinion on the feature request you have suggested as our experience seems different from yours.