Notification "Bell" Icon Change

%3CLINGO-SUB%20id%3D%22lingo-sub-10094%22%20slang%3D%22en-US%22%3ENotification%20%22Bell%22%20Icon%20Change%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-10094%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20been%20away%20for%20a%20couple%20of%20weeks%2C%20so%20please%20let%20me%20know%20if%20there's%20an%20announcement%20that%20I've%20missed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20Yammer%20notifications%20are%20no%20longer%20showing%20with%20a%20number%20in%20the%20upper%20right%20hand%20corner%20of%20the%20%22bell%22%20icon.%20Instead%20there's%20a%20little%20red%20dot%20there.%20This%20is%20occurring%20for%20a%20few%20of%20my%20users%20as%20well%20-%20whereas%20others%20are%20still%20being%20shown%20the%20numbers.%20Is%20there%20some%20A%2FB%20testing%20going%20on%20prior%20to%20a%20release%3F%20I%20wish%20I%20had%20the%20foresight%20to%20take%20a%20screenshot%20before%20clearing%20all%20of%20my%20notifications%20%3A-D.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-10094%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-12129%22%20slang%3D%22en-US%22%3ERe%3A%20Notification%20%22Bell%22%20Icon%20Change%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-12129%22%20slang%3D%22en-US%22%3ELooks%20like%20it's%20back!%20Thanks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-11851%22%20slang%3D%22en-US%22%3ERe%3A%20Notification%20%22Bell%22%20Icon%20Change%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-11851%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20numbers%20for%20notification%20should%20be%20back%20tomorrow.%20It%20was%20part%20of%20a%20small%20test%20we%20were%20working%20on%20but%20will%20now%20revert%20back%20to%20as%20it%20was%20before.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-11207%22%20slang%3D%22en-US%22%3ERe%3A%20Notification%20%22Bell%22%20Icon%20Change%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-11207%22%20slang%3D%22en-US%22%3E%3CP%3ERed%20Dot%20here%20as%20well.%26nbsp%3B%20I%20haven't%20checked%20the%20users%20in%20my%20tenant.%26nbsp%3B%20The%20red%20dot%20does%20not%20jump%20out%20like%20the%20number%20did.%26nbsp%3B%20I%20prefer%20the%20number.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-11147%22%20slang%3D%22en-US%22%3ERE%3A%20Notification%20%22Bell%22%20Icon%20Change%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-11147%22%20slang%3D%22en-US%22%3ESo%20I%20guess%20the%20question%20is%20-%20who%20from%20the%20Yammer%20team%20is%20going%20to%20address%20this%3F%20I%20would%20just%20like%20to%20know%20if%20this%20is%20something%20that's%20being%20tested%20to%20see%20if%20it'll%20stick%20or%20is%20it%20something%20that%20they're%20actively%20rolling%20out.%20I've%20gotten%20several%20complaints%20from%20users%20on%20my%20network%20who%20don't%20like%20the%20lack%20of%20a%20number%20so%20I'm%20curious%20if%20they're%20taking%20feedback%20on%20the%20matter.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-11133%22%20slang%3D%22en-US%22%3ERe%3A%20Notification%20%22Bell%22%20Icon%20Change%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-11133%22%20slang%3D%22en-US%22%3E%3CP%3ERed%20dot%20on%20my%20network%20too.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-11096%22%20slang%3D%22en-US%22%3ERe%3A%20Notification%20%22Bell%22%20Icon%20Change%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-11096%22%20slang%3D%22en-US%22%3E%3CP%3EMe%20too%2C%20back%20from%20holidays%20and%20the%20notification%20only%20has%20a%20little%20red%20dot.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-10155%22%20slang%3D%22en-US%22%3ERe%3A%20Notification%20%22Bell%22%20Icon%20Change%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-10155%22%20slang%3D%22en-US%22%3E%3CP%3EWell%20-%20glad%20to%20know%20I'm%20not%20crazy%20%3A-).%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-10115%22%20slang%3D%22en-US%22%3ERe%3A%20Notification%20%22Bell%22%20Icon%20Change%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-10115%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20I%20have%20been%20seeing%20the%20dot%20rather%20than%20a%20number%20for%20the%20last%20week%20or%20so%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-10108%22%20slang%3D%22en-US%22%3ERe%3A%20Notification%20%22Bell%22%20Icon%20Change%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-10108%22%20slang%3D%22en-US%22%3EI've%20also%20noticed%20the%20same%20thing.%20Wondered%20what%20was%20going%20on%20with%20it.%20Anyone%20else%20seeing%20this%3F%3C%2FLINGO-BODY%3E
Contributor

I've been away for a couple of weeks, so please let me know if there's an announcement that I've missed.

 

My Yammer notifications are no longer showing with a number in the upper right hand corner of the "bell" icon. Instead there's a little red dot there. This is occurring for a few of my users as well - whereas others are still being shown the numbers. Is there some A/B testing going on prior to a release? I wish I had the foresight to take a screenshot before clearing all of my notifications :-D.

9 Replies
I've also noticed the same thing. Wondered what was going on with it. Anyone else seeing this?

Yes I have been seeing the dot rather than a number for the last week or so as well.

Well - glad to know I'm not crazy :-). 

Me too, back from holidays and the notification only has a little red dot.

Red dot on my network too.

So I guess the question is - who from the Yammer team is going to address this? I would just like to know if this is something that's being tested to see if it'll stick or is it something that they're actively rolling out. I've gotten several complaints from users on my network who don't like the lack of a number so I'm curious if they're taking feedback on the matter.

Red Dot here as well.  I haven't checked the users in my tenant.  The red dot does not jump out like the number did.  I prefer the number. 

The numbers for notification should be back tomorrow. It was part of a small test we were working on but will now revert back to as it was before. 

Looks like it's back! Thanks.