7.1.18 - Alerts page cannot Count (still)

• 
  Hi @PDinCA
  
  I do think this is intended, though I will clarify that with the team - as you noticed it's not taking into account the filtering you may have done and gives the number of unread alerts you have at that level.
  
  So I have a server that shows "ServerName (165)" and when I filter it to only show the 40 Backup Overdue alerts, it still shows 165. Also, when I clear the filter, it tells me there are 170 alerts for that server, if I then uncheck "Read" in the filter, it then gives me the 165 that is indicated by the parenthesized number.
  
  As I said, I'll double check this, but I think we intend to let you know how many you haven't looked at overall.
  
  Kind regards,
  Alex

  Alex B February 28, 2018 20:36

  - 0 +
• 
  Thanks, Alex, but IMO that's a very bad decision for Red Gate to have made.
  
  Consider that, as you saw from the attached image, I have 7 groups under my server tree. I click on the root, giving me the entire list. I set the filter THERE.
  
  Red Gate says I must click down every node to see if any of my 21 servers has an alert of that kind, AFTER I have clicked on one of my group nodes to see "how do I fare in this group of servers?"
  
  It makes no sense to show overall numbers when I have explicitly filtered to see the wood for the trees. My count-granularity should always reflect filtering at all levels. It's uninformative to see "you have 350 unread Alerts" all the time, when the issue I am looking at applies to a handful of servers and a couple of handfuls of unread alerts of my filter type...
  
  At worst, please give us a configuration that says "always show total unread" or "Show filter-level unread" so the tree makes sense and I can navigate via the tree rather than by the jumble of alerts in the all-servers detail list...
  
  Thanks for your consideration.

  PDinCA February 28, 2018 20:51

  - 0 +
• 
  Hi @PDinCA
  
  That is a fair point and the team agree - though I do still think it would be good to be made aware of the total number of unread in case one forgets they've filtered the view perhaps... Maybe something like:
  
  ServerName (165 - 40 filtered)
  or
  ServerName (165[40])
  
  Or something a UX person is probably better able to come up with
  
  Kind regards,
  Alex

  Alex B March 01, 2018 12:36

  - 0 +
• 
  Thanks for the warm reception re the filtered count, Alex.
  
  Yes, something along the lines of the dual-number display would be great. I'd vote for filter-count first, as in 5 of 135, bolded for not-read as currently exhibited.
  
  Cheers!

  PDinCA March 01, 2018 18:31

  - 0 +

Add comment

Please sign in to leave a comment.