We’ve had a problem with filtering fixlets since we upgraded from BES 6.
It started when we upgraded to 7.0.1.376 and we still have the problem now (upgraded to 7.0.7.96 last night)
If we filter fixlets by site > enterprise security we can see all the enterprise security fixlets in the right-hand pane as expected
But if we filter by site > enterprise security > source release date not all fixlets will display.
For instance, even though it may display 11/12/2007 (70) in the left-hand pane, thus indicating 70 fixlets under this date, when we select this we just see “No Fixlet messages meet the filter criteria” in the right-hand pane.
I’ve attached screenshot to help with the explanation
This is happening for all console users and whether or not we’re logged in with operator or master accounts.
It doesn’t happen for all dates, some dates display the fixlets quite happily so it’s a little confusing.
It will also occur if we just filter by source release date alone.
Has anyone come across this or have any suggestions what to look at?
Cheers
Steve
P.S. Trying to upload attachment but it isn’t letting me so please try following linke…
That certainly looks weird. I looked in my console and I don’t see any Fixlets from 3/8/2000 in the Enterprise security site. So, I think that the right side is correctly showing no results and its the Filter on the left side that is incorrectly showing Fixlets. My guess would be that these fixlets existed at one point but have since been removed and for some reason the filters aren’t updating that the Fixlets have been removed.
Could you try the following?
Does it happen on new installs of the BES Console?
Does clearing the BES Console cache fix the problem? (File->Preferences->Clear Cache)
I think he is using a different date format, which I suspect is somehow related to this issue…
Steve, I am wondering if it only seems to occur if there are preceding “0”, like maybe “03/08/2000” causes an issue, but not “30/12/2000”? Just a shot in the dark…
This is good info and I will file a bug so we can fix this in future versions. My guess is that if you switch to the American-style dates, it will workaround this issue.