Shane Ardell created METRON-2337: ------------------------------------ Summary: Resolve stale data state / message inconsistencies Key: METRON-2337 URL: https://issues.apache.org/jira/browse/METRON-2337 Project: Metron Issue Type: Bug Reporter: Shane Ardell
As pointing out in [PR #1527|https://github.com/apache/metron/pull/1527#pullrequestreview-298193000], there are a few scenarios where the state of the alerts table data and the stale data state message are not in sync. User scenario #1: User switch to manual query mode Making changes on the filtering Pressing search and receives another set of alerts Then moves back to Query Builder mode This could turn the UI to a "stale data state" bc the list of alerts filtered by the previously shown manual query and the visible filters and the data no longer in sync. User scenario #2: User switch to manual query mode Making changes in the filtering UI should turn to a "stale data state" to keep behavior consistent across ace and manual editors. User scenario #3: User switch to manual query mode Making changes in the filtering UI should turn to a "stale data state" to keep behavior consistent across ace and manual editors. But when User switch back without updating the data based on the manual filter "Stale data state" should be cleared hence the data is in sync with the shown filters again. User scenario #4: User move to manual mode Making changes in the filtering Pressing search and receiving another set of data Then switching to query builder mode UI should be in a "stale data state" as described in scenario #1 If User switch back to manual mode "stale data state" should be cleared hence the data is in sync with the filters again -- This message was sent by Atlassian Jira (v8.3.4#803005)