Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide an option to depict that there are new notifications available in tendrl UI #154

Open
shtripat opened this issue Jan 23, 2018 · 3 comments

Comments

@shtripat
Copy link
Member

If there are new notifications which are not yet viewed, there should be a mechanism to communicate the same to end user in UI. There should be some marker at top right bell icon (either a red * mark or a new notifications count) which communicates that there are few not viewed notifications.

@r0h4n @nthomas-redhat @julienlim @mbukatov plz check and ack.

@julienlim
Copy link
Member

@shtripat This is already commented on at Alerts icon (bell icon) on Web Admin home page needs to show/indicate if there are unread events/alerts and Bugzilla #1517246.

Per @mcarrano, "The appearance/behavior of the bell icon in the masthead is specified in PatternFly here: http://www.patternfly.org/pattern-library/application-framework/masthead/. When there are new or unread alerts present, a blue badge should be added to the upper right corner of the icon. We did not include a count value because it will not scale well from a readability standpoint."

@r0h4n @nthomas-redhat @mbukatov @gnehapk @cloudbehl @a2batic

@nthomas-redhat
Copy link
Contributor

nthomas-redhat commented Jan 25, 2018

Per @mcarrano, "The appearance/behavior of the bell icon in the masthead is specified in PatternFly here: http://www.patternfly.org/pattern-library/application-framework/masthead/. When there are new or unread alerts present, a blue badge should be added to the upper right corner of the icon. We did not include a count value because it will not scale well from a readability standpoint."

@julienlim, when we discussed this, the concern raised was wrt backend change required. But with this proposal I assume that no backend changes are required. Looks good to me

@gnehapk , please take a look at this as well

@r0h4n r0h4n added this to the Milestone 5 (2018) milestone Apr 20, 2018
@shtripat
Copy link
Member Author

@gnehapk isnt this already done? Should we close this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants