Bug 1510962 - Events are missing display all option
Summary: Events are missing display all option
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: All
OS: All
medium
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Alexander Wels
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-08 13:32 UTC by Lukas Svaty
Modified: 2017-12-20 10:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-12-20 10:59:42 UTC
oVirt Team: UX
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: blocker+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 83794 0 master MERGED webadmin: display all alerts/events 2017-11-09 01:04:50 UTC

Description Lukas Svaty 2017-11-08 13:32:23 UTC
Description of problem:
In 4.1 we were able to clear event/all events, and additionally display all of them which will 'unclear' all and display them in events. In 4.2 this is not possible as we do not have right click context menu. Therefore if you clear an event it's gone forever.

Comment 1 Red Hat Bugzilla Rules Engine 2017-11-08 13:53:16 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Petr Matyáš 2017-11-14 15:35:38 UTC
Verified on ovirt-engine-4.2.0-0.0.master.20171113223918.git25568c3.el7.centos.noarch

Comment 3 Sandro Bonazzola 2017-12-20 10:59:42 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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


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