Last modified: 2014-11-12 15:07:20 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.
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.
Change 158239 had a related patch set uploaded by Spage: Add reverse chronological ordering to unread notifications https://gerrit.wikimedia.org/r/158239
Change 158239 merged by jenkins-bot: Add reverse chronological ordering to unread notifications https://gerrit.wikimedia.org/r/158239
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?