[ 
https://issues.apache.org/jira/browse/METRON-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16175337#comment-16175337
 ] 

ASF GitHub Bot commented on METRON-1189:
----------------------------------------

Github user merrimanr commented on the issue:

    https://github.com/apache/metron/pull/762
  
    I researched the saveRefreshState() and restoreRefreshState() addition and 
it uncovered a bug which then uncovered a problem with how our UI works.
    
    The bug was that the selectedAlerts field (checkboxes in the list) was not 
getting cleared on any of the bulk actions.  As refreshes happened the 
checkboxes would disappear and be replaced by new results but that that field 
would constantly grow because they were never unchecked on the previous page. 
It was benign before this PR but is now causing a lot of duplicate REST 
requests.  We need to figure out the right way to clear these when a bulk 
action finishes but there is also another issue.
    
    As I was testing for this I realized when I set the refresh rate to a high 
rate I had to click quickly or the page would change and I would lose my 
selections.  What @iraghumitra mentions above is a pause while the REST 
requests are being processed but I think it makes sense to pause even earlier, 
whenever you have a checkbox checked.  I can obviously get it to work if I 
pause it but I think that's a better UX.


> Add alert escalation to the Alerts UI
> -------------------------------------
>
>                 Key: METRON-1189
>                 URL: https://issues.apache.org/jira/browse/METRON-1189
>             Project: Metron
>          Issue Type: New Feature
>            Reporter: Ryan Merriman
>            Assignee: Ryan Merriman
>
> The PR is a follow on to https://issues.apache.org/jira/browse/METRON-1127.  
> We need a way to escalate alerts in the alerts UI so that a user can selects 
> alerts and send them to the escalate REST endpoint.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to