This problem may reveal itself with alert history not showing up without a refresh or possibly with ancestry hover generating an exception.
make sure you have some alert history for various resources, at least one in a group.
Try Global dash recent alerts
Try resource dash recent alerts
Try resource alert history tab
Try group dash recent alerts
Try group alert history tab
Try hover on ancestry fields quickly after rendering of the rows.
Make sure refresh is not required to see the initial list of rows.
make sure portlet config is honored.
i am actually seeing the original behavior. i create an alert that fires very frequently (on the platform resource, if free memory > 0). i observe that history does not display any alerts. if i click 'refresh', then the fired alerts appear. this would seem to be the original behavior. will discuss with jshaughn.
jshaughn, can you clarify?
clarification: if you are sitting on alerts-->history ...you DO need to click refresh (as I observed and documented above). this issue is specifically if you navigate to alerts-->history that you don't additionally need to click refresh. this behavior i am seeing. assigning back to on_qa to verify the various scenarios described in comment 1
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.