Use Jira favicon instead of project specific favicon

[Robin Eggenkamp]

Recently the favicon of our hosted Jira started to use the avatar of projects as favicon. This makes it difficult to find the Jira tab in the browser between tabs of our own website.

How can I revert back to using the Jira favicon, without setting the avatar of each project to the Jira icon?

[Deleted user]

Our company created custom set of icons/illustrations for all projects when the feature to match favicon and project image was rolled out. And after a few days enjoying those, now all our favicons reverted back to jira logo. How to get back having the favicon derived from a project image?

[Dave Elkan]

Me too! I found this feature quite useful to differentiate pinned tabs for specific projects. Now they're all the same again! Frustrating!

[Mike Schmitt]

I'm here to chime in too - I had gotten used to this (seeing it as a marked improvement since at all times I'm dealing with tabs for 2 or more projects which otherwise get mixed up), and now it's gone.

[Jenny Colebourn]

Agreed! I found the feature very useful in keeping my bookmarks tidy on Chrome. Would love to see the option return.

[michael.coffey]

I agree with the having the project avatar show.  I could easily distinguish between the multiple projects that I have tabs open for. 

[Pavel Dobrý]

I totally agree. That was a bad move and UX fail. Jira Cloud must use the favicon defined in the System settings.

[Diego]

Hey, hello there!

This is indeed a new feature being rolled out. This does not affect 100% of the user base yet since it is still being rolled out.

You can leave your feedback about the feature right here:

• Optional use of project avatar as browser tab icon (favicon) 

Just making sure everyone gets a notification about this:

@Robin Eggenkamp 

@Dan 

@dennis.alferink 

@Calla 

@Jack Brickey

Let us hear from you!

[Wade P Lorber]

How do we opt out of this feature? Our users find it confusing.

[Dan]

Why does it say "optional" if there is no way to opt out and revert to the Jira icon?

[Jack Brickey]

@Dan i think simply because of the author's word choices.

[Deleted user]

Would like to opt out. Very hard to understand which tab I need to navigate to.

[juan.angot]

Would love to opt out as well. 

[Mike Schmitt]

I'd like this feature back, as it was a dramatic improvement in my case - having all tabs forced to the same default "blue diamond" logo is profoundly confusing after getting used to them all reflecting their avatar images.  I would be fine with opting-in via Project Settings.  It seems like this should be an easy add.

[Dan]

Also happened in our Jira Cloud and is very frustrating.  The Jira favicon was an easy way to distinguish the tab was a Jira tab and we really want it back!

[dennis.alferink]

This happened on our Jira Cloud instance as well. 

Previously the Jira icon was used as the favicon. Since an update somewhere last week it changed to the project icon as the favicon. This is very confusing since the same icon is used as a favicon for both Jira and the Project itself (the website we're working on)

We'd like to have the Jira logo as favicon back. 

[Calla]

This has happened in our Jira Cloud instance as well; I'm happy to provide screenshots if needed, but they would be essentially the same as what has already been shared.

[Jack Brickey]

Can you provide a screenshot. Someone else posted this same issue a couple of days ago.

[Robin Eggenkamp]

On https://xxx.atlassian.net/secure/admin/LookAndFeel!default.jspa the Jira icon is set:

But while for example on a Kanban board the favicon changes to the avatar set through the project settings: https://xxx.atlassian.net/secure/project/EditProject!default.jspa?pid=10500

This behaviour changed a few days ago, before it correctly displayed the favicon set as in the above screenshot.

[Matvey Gerasimov]

Here you go, Jack!

[Jack Brickey]

So I’m not sure TBH. But certainly it appears some change was rolled out to your instances that resulted in the new behavior. I can only suggest that you reach out to Atlassian Support.