Bug 1479922

Summary: The notification events are out of order
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: UI - OPSAssignee: Dávid Halász <dhalasz>
Status: CLOSED ERRATA QA Contact: Satyajit Bulage <sbulage>
Severity: medium Docs Contact:
Priority: high    
Version: 5.8.0CC: akarol, hkataria, jhardy, mpovolny, obarenbo, rspagnol, simaishi
Target Milestone: GAKeywords: ZStream
Target Release: 5.8.2   
Hardware: x86_64   
OS: Linux   
Whiteboard: notification
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1469534 Environment:
Last Closed: 2017-10-24 00:37:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Bug Depends On: 1469534    
Bug Blocks:    

Comment 2 CFME Bot 2017-08-09 18:33:24 UTC
New commit detected on ManageIQ/manageiq-ui-classic/fine:

commit f958942717d11ee414ebe06bf8cc53a5b416045e
Author:     Martin Hradil <himdel@seznam.cz>
AuthorDate: Wed Jul 19 17:27:09 2017 +0200
Commit:     Satoe Imaishi <simaishi@redhat.com>
CommitDate: Wed Aug 9 14:28:30 2017 -0400

    Merge pull request #1713 from skateman/notifications-inorder
    Sort asynchronously arrived notifications by timestamp in the drawer
    (cherry picked from commit 06dd3f386d0355ad77312092b947c1f4ad134801)

 app/assets/javascripts/services/event_notifications_service.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 3 Satyajit Bulage 2017-09-07 05:47:35 UTC
Able to see Notifications in proper order i.e. Latest notification on top and older notification below that.

Verified Version:

Comment 4 Dávid Halász 2017-10-12 16:01:53 UTC
*** Bug 1491820 has been marked as a duplicate of this bug. ***

Comment 6 errata-xmlrpc 2017-10-24 00:37:35 UTC
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.