Bug 1637015

The position of them follows our design standard, PatternFly. Example: https://www.patternfly.org/pattern-library/communication/toast-notifications/  (at the bottom)

What version of engine is this? It could also be the case that you're experiencing too many notifications and would like to disable them. We added this capability in a 4.2.z update. See Bug 1608362.

[The notifications are supposed to clear automatically after a few seconds, so you technically don't need to click the 'close' button on each of them.]

Hi Greg, 

they're running the latest version of engine. 
So the do not disturb functionality should be available. Is this something I can enable pro actively, based on my account or is it only possible to enable when 3 or more messages are shown.

The automatic-close feature might be fine, but when the message is covering required buttons, it's the same issue. I need to stop or interrupt my work to wait or confirm a message, before I can click on the button.

As the recommendation of patternfly, messages shown in top-right corner, is there a possibility to change this by some kind of configuration?

(In reply to Steffen Froemer from comment #4)
> Hi Greg, 
> 
> they're running the latest version of engine. 
> So the do not disturb functionality should be available. Is this something I
> can enable pro actively, based on my account or is it only possible to
> enable when 3 or more messages are shown.

Currently it shows when 3, but we can make it configurable.

> 
> The automatic-close feature might be fine, but when the message is covering
> required buttons, it's the same issue. I need to stop or interrupt my work
> to wait or confirm a message, before I can click on the button.
> 
> As the recommendation of patternfly, messages shown in top-right corner, is
> there a possibility to change this by some kind of configuration?

I don't want to move the location, but we can add a feature to disable them per-user. Converting to an RFE.

(In reply to Greg Sheremeta from comment #5)

> 
> Currently it shows when 3, but we can make it configurable.
Yes, would make more sense. 

> 
> I don't want to move the location, but we can add a feature to disable them
> per-user. Converting to an RFE.
From UX perspective I does not like, if notification hide items, which I need for my work, but it's you, who will decide.
But I agree in adding feature to completely disable notification and also I would see only notification for tasks of current user-session.

From a UX and PatternFly perspective I think for the time being keeping the placement of the toast notifications but extending the capabilities of notification settings is the best option. I reached out to the larger UX group asking about notifications in other products and it sounds like others have been experiencing a similar issue with the placement of the toast notifications as well.

We can easily tweak the current "Do Not Disturb" functionality and get a huge usability improvement.

Currently the buttons show when there are 3+ toast notifications showing, but we can just make the buttons show when any toasts are showing. Should be a tiny low risk change. Targeting for 4.3.

(In reply to Greg Sheremeta from comment #8)
> We can easily tweak the current "Do Not Disturb" functionality and get a
> huge usability improvement.
> 
> Currently the buttons show when there are 3+ toast notifications showing,
> but we can just make the buttons show when any toasts are showing. Should be
> a tiny low risk change. Targeting for 4.3.

I agree in doing this for the first step. But it still need to be configurable in future. If customer need to click DND-button every time he login again.
The best solution still might be only show notifications from the users tasks

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Created attachment 1525219 [details]
notification Dismiss and Do Not Disturb buttons

Created attachment 1525220 [details]
notifications buttons demo

(In reply to Steffen Froemer from comment #9)
> (In reply to Greg Sheremeta from comment #8)
> > We can easily tweak the current "Do Not Disturb" functionality and get a
> > huge usability improvement.
> > 
> > Currently the buttons show when there are 3+ toast notifications showing,
> > but we can just make the buttons show when any toasts are showing. Should be
> > a tiny low risk change. Targeting for 4.3.
> 
> I agree in doing this for the first step.

For the first step, I've posted a patch and a demo of the 'Dismiss All' and 'Do Not Disturb' buttons working properly for 1+ Toast Notifications showing.

> But it still need to be configurable in future. If customer need to click DND-button every time he
> login again.

Not every login -- once per day is the maximum snooze time.

> The best solution still might be only show notifications from the users tasks

We can look into this later, but it will be some time before we get to it.

>> The best solution still might be only show notifications from the users tasks
> We can look into this later, but it will be some time before we get to it.

Spinning out a new BZ 1679110

WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]

For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]

For more info please contact: rhv-devops

Verified on ovirt-engine-4.3.1.1-0.1.el7.noarch.
Dismiss and snooze buttons are present and function correctly.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:1085