Bug 1396887 - Illegible number for service events on the bell icon of the notifications feature
Summary: Illegible number for service events on the bell icon of the notifications fea...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - Service
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: cfme-future
Assignee: Allen W
QA Contact: Dave Johnson
URL:
Whiteboard: notifications
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-21 05:31 UTC by Suyog Sainkar
Modified: 2016-11-29 14:16 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-28 23:34:28 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)
Notifications number (3.13 KB, image/png)
2016-11-21 05:31 UTC, Suyog Sainkar
no flags Details

Description Suyog Sainkar 2016-11-21 05:31:49 UTC
Created attachment 1222295 [details]
Notifications number

Description of problem:

The number on the bell icon of the notifications feature notifying the number of service events is illegible. (See attached screen capture)

Version-Release number of selected component (if applicable): 

Version: 5.7.0.10-beta3.20161109111947_9a61b18


How reproducible:


Steps to Reproduce:

1. Log in to the SSUI.
2. Add a service to shopping cart, order shopping cart items, or start a service - basically anything that the system would generate a message (event) as part of the notifications feature.
3. See the number on the bell icon of the notifications feature.

Actual results:
Indecipherable text (number) on the bell icon

Expected results:

Clear text (number) on the bell icon (as on the shopping cart icon)

Comment 3 Serena 2016-11-23 14:33:11 UTC
The design was to not have a number on the bell icon for notifications.  Although this is consistent with the badge for the shopping cart, the UX team feels this is necessary.  Currently with the way that the notifications work, this number can be very large, thus the badge doesn't scale.  We took the concept of having a badge with no number ( which seems to be prevalent in different apps outside of RH ).

Our initial design was to show a "dot" inside the circle (Slack does this).  We felt that showing nothing at all ( as github does ) could be construed as having something missing.  Note that the "." in the badge is something that we are doing in both the SSUI and the Ops UI.  

I'd suggest that we remove this fix for having a number in the badge since it is not scalable.

Comment 4 Dave Johnson 2016-11-23 17:14:41 UTC
I was kind of thinking what Serena was saying in comment3 when we went through triage.  Comment 2 PR is already merged, Serena, I believe you are saying we should revert that, correct?  And this move this to CLOSED NOTABUG, correct?

Comment 5 Serena 2016-11-28 23:34:28 UTC
Yes Dave, that is my suggestion.  Moving to CLOSED NOTABUG.

Comment 6 Jason Frey 2016-11-29 05:52:12 UTC
We should leave this open until the PR is actually reverted.  As it stands, if this is closed, there is no ticket that is accounting for the revert.

Comment 7 Allen W 2016-11-29 14:04:54 UTC
https://github.com/ManageIQ/manageiq-ui-service/pull/360

after much anticipation 🌮

Comment 8 Allen W 2016-11-29 14:16:32 UTC
https://github.com/ManageIQ/manageiq-ui-service/pull/360

after much anticipation 🌮


Note You need to log in before you can comment on or make changes to this bug.