Last modified: 2014-11-12 15:07:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T71919, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69919 - most recent message notifications should appear first in Echo flyout
most recent message notifications should appear first in Echo flyout
Status: PATCH_TO_REVIEW
Product: MediaWiki extensions
Classification: Unclassified
Echo (Other open bugs)
master
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-22 19:21 UTC by spage
Modified: 2014-11-12 15:07 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description spage 2014-08-22 19:21:30 UTC
I had a lot of unread Flow "message" notifications. Someone created a new topic.
My Echo notification count went up, but I couldn't see the new notification because the flyout showed earlier "message" notifications.
Comment 1 bsitu 2014-08-22 20:11:22 UTC
This was done on purpose.  The notification is not optimized for ordering unread notifications, I guess we could alter the index for the table, I am very reluctant going with this route.  On the other hand, users shouldn't have that many unread notifications, I guess it's okay to do an ordering.
Comment 2 Gerrit Notification Bot 2014-09-09 19:21:24 UTC
Change 158239 had a related patch set uploaded by Spage:
Add reverse chronological ordering to unread notifications

https://gerrit.wikimedia.org/r/158239
Comment 3 Gerrit Notification Bot 2014-10-07 18:01:51 UTC
Change 158239 merged by jenkins-bot:
Add reverse chronological ordering to unread notifications

https://gerrit.wikimedia.org/r/158239
Comment 4 Andre Klapper 2014-11-12 15:07:20 UTC
All patches mentioned in this report were merged or abandoned - is there more work left to do here (if yes: please reset the bug report status to NEW or ASSIGNED), or can you close this ticket as RESOLVED FIXED?

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


Navigation
Links