[jira] [Updated] (METRON-2337) [UI] Resolve stale data state / message inconsistencies in Alerts UI
[ https://issues.apache.org/jira/browse/METRON-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2337: - Summary: [UI] Resolve stale data state / message inconsistencies in Alerts UI (was: Resolve stale data state / message inconsistencies) > [UI] Resolve stale data state / message inconsistencies in Alerts UI > > > Key: METRON-2337 > URL: https://issues.apache.org/jira/browse/METRON-2337 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > > 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)
[jira] [Created] (METRON-2337) Resolve stale data state / message inconsistencies
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)
[jira] [Created] (METRON-2328) [UI] Stale data state inconsistencies in the Alerts UI
Shane Ardell created METRON-2328: Summary: [UI] Stale data state inconsistencies in the Alerts UI Key: METRON-2328 URL: https://issues.apache.org/jira/browse/METRON-2328 Project: Metron Issue Type: Bug Reporter: Shane Ardell Link to original discussion: https://github.com/apache/metron/pull/1527#pullrequestreview-298193000 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)
[jira] [Assigned] (METRON-2325) Wrong validation message appears when clicking on input of existing group
[ https://issues.apache.org/jira/browse/METRON-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2325: Assignee: Shane Ardell > Wrong validation message appears when clicking on input of existing group > - > > Key: METRON-2325 > URL: https://issues.apache.org/jira/browse/METRON-2325 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Attachments: Screen Shot 2019-11-20 at 6.23.28 PM.png > > > After a user creates a parser group and tries to edit the details of the > group, the name input becomes readonly. However, we have a keyup event that's > active and causes the existing group validation message to appear. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (METRON-2325) Wrong validation message appears when clicking on input of existing group
Shane Ardell created METRON-2325: Summary: Wrong validation message appears when clicking on input of existing group Key: METRON-2325 URL: https://issues.apache.org/jira/browse/METRON-2325 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell Attachments: Screen Shot 2019-11-20 at 6.23.28 PM.png After a user creates a parser group and tries to edit the details of the group, the name input becomes readonly. However, we have a keyup event that's active and causes the existing group validation message to appear. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (METRON-2281) [UI] Eliminate Create new/merge screen
[ https://issues.apache.org/jira/browse/METRON-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2281: Assignee: Shane Ardell > [UI] Eliminate Create new/merge screen > -- > > Key: METRON-2281 > URL: https://issues.apache.org/jira/browse/METRON-2281 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When the user drags a standalone parser and drops it to sub-parser of a group > there is a choice with two options. > One is to "merge" the standalone parser into the group. Other is to "create > new" group out of the two involved parsers. This is only supported by the > backend if we remove the originally grouped parser from its previous group > (as the first step of the transaction) and then create a new one (second step > of the transaction). > Due to the massive complexities that come with this and the fact that there > are other ways to create a new group available to the user (and therefore > does not add value to the user), those of us working on this feature have > decided to remove it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (METRON-2323) Increase unit test coverage for Alerts List
Shane Ardell created METRON-2323: Summary: Increase unit test coverage for Alerts List Key: METRON-2323 URL: https://issues.apache.org/jira/browse/METRON-2323 Project: Metron Issue Type: Improvement Reporter: Shane Ardell -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (METRON-2318) Merge master into feature branch
Shane Ardell created METRON-2318: Summary: Merge master into feature branch Key: METRON-2318 URL: https://issues.apache.org/jira/browse/METRON-2318 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell The feature branch is once again out-of-date, and there are many conflicts to resolve. For this reason, I'm creating a ticket to separate the resolved conflicts with other work. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (METRON-2306) [UI] Grok parsers' have duplicate timestampField
[ https://issues.apache.org/jira/browse/METRON-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2306: Assignee: Shane Ardell > [UI] Grok parsers' have duplicate timestampField > > > Key: METRON-2306 > URL: https://issues.apache.org/jira/browse/METRON-2306 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Attachments: Screen Shot 2019-10-30 at 4.41.14 PM.png, Screen Shot > 2019-10-30 at 4.41.21 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > > Right now, existing Grok parsers in the UI have two timestamp name fields. > One is a field is used to force a user to add a name in the case of creating > a grok parser, and the other allows the user to edit the existing name (or > delete it altogether!). See the attached image for reference. > A simple fix would be to hide the first mentioned instance if the parser > isn't new. Another possibility is just removing the first field altogether > and requiring the parser config object to have the timestampField property if > it's a Grok parser. We also might want to remove the capability to delete the > timestampField in the second instance since that's a required field for Grok > parsers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (METRON-2306) [UI] Grok parsers' have duplicate timestampField
[ https://issues.apache.org/jira/browse/METRON-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2306: - Description: Right now, existing Grok parsers in the UI have two timestamp name fields. One is a field is used to force a user to add a name in the case of creating a grok parser, and the other allows the user to edit the existing name (or delete it altogether!). See the attached image for reference. A simple fix would be to hide the first mentioned instance if the parser isn't new. Another possibility is just removing the first field altogether and requiring the parser config object to have the timestampField property if it's a Grok parser. We also might want to remove the capability to delete the timestampField in the second instance since that's a required field for Grok parsers. was: Right now, existing Grok parsers in the UI have two timestamp name fields. One is a field is used to force a user to add a name in the case of creating a grok parser, and the other allows the user to edit the existing name (or delete it altogether!). See the attached image for reference. A simple fix would be to hide the first mentioned instance if the parser isn't new. We also might want to remove the capability to delete the timestampField in the second instance since that's a required field for Grok parsers. > [UI] Grok parsers' have duplicate timestampField > > > Key: METRON-2306 > URL: https://issues.apache.org/jira/browse/METRON-2306 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > Attachments: Screen Shot 2019-10-30 at 4.41.14 PM.png, Screen Shot > 2019-10-30 at 4.41.21 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > > Right now, existing Grok parsers in the UI have two timestamp name fields. > One is a field is used to force a user to add a name in the case of creating > a grok parser, and the other allows the user to edit the existing name (or > delete it altogether!). See the attached image for reference. > A simple fix would be to hide the first mentioned instance if the parser > isn't new. Another possibility is just removing the first field altogether > and requiring the parser config object to have the timestampField property if > it's a Grok parser. We also might want to remove the capability to delete the > timestampField in the second instance since that's a required field for Grok > parsers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (METRON-2306) [UI] Grok parsers' have duplicate timestampField
[ https://issues.apache.org/jira/browse/METRON-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2306: - Summary: [UI] Grok parsers' have duplicate timestampField (was: [UI] Grok parsers' timestamp field should be hidden if not new) > [UI] Grok parsers' have duplicate timestampField > > > Key: METRON-2306 > URL: https://issues.apache.org/jira/browse/METRON-2306 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > Attachments: Screen Shot 2019-10-30 at 4.41.14 PM.png, Screen Shot > 2019-10-30 at 4.41.21 PM.png > > > Right now, existing Grok parsers in the UI have two timestamp name fields. > One is a field is used to force a user to add a name in the case of creating > a grok parser, and the other allows the user to edit the existing name (or > delete it altogether!). See the attached image for reference. > A simple fix would be to hide the first mentioned instance if the parser > isn't new. We also might want to remove the capability to delete the > timestampField in the second instance since that's a required field for Grok > parsers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (METRON-2304) Update node and npm version to LTS releases
[ https://issues.apache.org/jira/browse/METRON-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2304: Assignee: Shane Ardell > Update node and npm version to LTS releases > --- > > Key: METRON-2304 > URL: https://issues.apache.org/jira/browse/METRON-2304 > Project: Metron > Issue Type: Improvement >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We are currently using node 9.11.1 and npm 6.2.0 in the project (this is > specified in both the Alerts UI and Management UI pom.xml files). > This version of node is no longer supported. Per their documents, "Production > applications should only use Active LTS or Maintenance LTS releases." The > current active LTS release is 10.17.0. The matching npm version is 6.11.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (METRON-2306) [UI] Grok parsers' timestamp field should be hidden if not new
[ https://issues.apache.org/jira/browse/METRON-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2306: - Summary: [UI] Grok parsers' timestamp field should be hidden if not new (was: [UI] Grok parsers' timestamp field should be hidden) > [UI] Grok parsers' timestamp field should be hidden if not new > -- > > Key: METRON-2306 > URL: https://issues.apache.org/jira/browse/METRON-2306 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > Attachments: Screen Shot 2019-10-30 at 4.41.14 PM.png, Screen Shot > 2019-10-30 at 4.41.21 PM.png > > > Right now, existing Grok parsers in the UI have two timestamp name fields. > One is a field is used to force a user to add a name in the case of creating > a grok parser, and the other allows the user to edit the existing name (or > delete it altogether!). See the attached image for reference. > A simple fix would be to hide the first mentioned instance if the parser > isn't new. We also might want to remove the capability to delete the > timestampField in the second instance since that's a required field for Grok > parsers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (METRON-2306) [UI] Grok parsers' timestamp field should be hidden
Shane Ardell created METRON-2306: Summary: [UI] Grok parsers' timestamp field should be hidden Key: METRON-2306 URL: https://issues.apache.org/jira/browse/METRON-2306 Project: Metron Issue Type: Bug Reporter: Shane Ardell Attachments: Screen Shot 2019-10-30 at 4.41.14 PM.png, Screen Shot 2019-10-30 at 4.41.21 PM.png Right now, existing Grok parsers in the UI have two timestamp name fields. One is a field is used to force a user to add a name in the case of creating a grok parser, and the other allows the user to edit the existing name (or delete it altogether!). See the attached image for reference. A simple fix would be to hide the first mentioned instance if the parser isn't new. We also might want to remove the capability to delete the timestampField in the second instance since that's a required field for Grok parsers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (METRON-2304) Update node and npm version to LTS releases
Shane Ardell created METRON-2304: Summary: Update node and npm version to LTS releases Key: METRON-2304 URL: https://issues.apache.org/jira/browse/METRON-2304 Project: Metron Issue Type: Improvement Reporter: Shane Ardell We are currently using node 9.11.1 and npm 6.2.0 in the project (this is specified in both the Alerts UI and Management UI pom.xml files). This version of node is no longer supported. Per their documents, "Production applications should only use Active LTS or Maintenance LTS releases." The current active LTS release is 10.17.0. The matching npm version is 6.11.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (METRON-2281) [UI] Eliminate Create new/merge screen
Shane Ardell created METRON-2281: Summary: [UI] Eliminate Create new/merge screen Key: METRON-2281 URL: https://issues.apache.org/jira/browse/METRON-2281 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell When the user drags a standalone parser and drops it to sub-parser of a group there is a choice with two options. One is to "merge" the standalone parser into the group. Other is to "create new" group out of the two involved parsers. This is only supported by the backend if we remove the originally grouped parser from its previous group (as the first step of the transaction) and then create a new one (second step of the transaction). Due to the massive complexities that come with this and the fact that there are other ways to create a new group available to the user (and therefore does not add value to the user), those of us working on this feature have decided to remove it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (METRON-2251) Update with the latest master branch
[ https://issues.apache.org/jira/browse/METRON-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2251: Assignee: Shane Ardell > Update with the latest master branch > > > Key: METRON-2251 > URL: https://issues.apache.org/jira/browse/METRON-2251 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > This branch is really out-of-date with the current master branch of Metron. > In addition to resolving conflicts, both UIs are up to Angular 7, which means > we have to update code to accommodate for breaking changes, stricter type > checking, etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (METRON-2277) Update sensor effect tests to use mock store and actions
Shane Ardell created METRON-2277: Summary: Update sensor effect tests to use mock store and actions Key: METRON-2277 URL: https://issues.apache.org/jira/browse/METRON-2277 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell After updating the version of NgRx and Angular we use, 2 tests fail in the sensor spec. I looked into fixing them, but when I reviewed the spec file I noticed we are relying on the actual store and actions to test effects. We should update the spec file to use the test helpers provided by ngrx, as mentioned [here|https://ngrx.io/guide/effects/testing]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (METRON-2257) Metron-Alerts GUI testing failing on MacOS builds
[ https://issues.apache.org/jira/browse/METRON-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2257: Assignee: Shane Ardell > Metron-Alerts GUI testing failing on MacOS builds > - > > Key: METRON-2257 > URL: https://issues.apache.org/jira/browse/METRON-2257 > Project: Metron > Issue Type: Bug >Reporter: Dale Richardson >Assignee: Shane Ardell >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > Since [METRON-2243 [UI] Update npm dependencies to resolve audit warnings > (s…|https://github.com/apache/metron/commit/edc449ffa6be51749f6a3b100bf6a0a33755e50c] > > (edc449ffa6be51749f6a3b100bf6a0a33755e50c) was merged with Master on 3rd > September 2019, Metron-Alerts has a number of GUI tests that fail when run on > MacOS (at least). Interestingly these tests did not appear to fail on the > Travis builds (which I'm led to believe run on Ubuntu). -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (METRON-2251) Update with the latest master branch
Shane Ardell created METRON-2251: Summary: Update with the latest master branch Key: METRON-2251 URL: https://issues.apache.org/jira/browse/METRON-2251 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell This branch is really out-of-date with the current master branch of Metron. In addition to resolving conflicts, both UIs are up to Angular 7, which means we have to update code to accommodate for breaking changes, stricter type checking, etc. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (METRON-2243) [UI] Update npm dependencies to resolve audit warnings
[ https://issues.apache.org/jira/browse/METRON-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2243: Assignee: Shane Ardell > [UI] Update npm dependencies to resolve audit warnings > -- > > Key: METRON-2243 > URL: https://issues.apache.org/jira/browse/METRON-2243 > Project: Metron > Issue Type: Improvement >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > After running `npm audit` in both UIs, we have a few dependencies and quite a > few nested dependencies needing version updates. This should be as simple as > running `npm audit fix`, although there may be a few dependencies needing > major version updates that require manual updates. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (METRON-2243) [UI] Update npm dependencies to resolve audit warnings
Shane Ardell created METRON-2243: Summary: [UI] Update npm dependencies to resolve audit warnings Key: METRON-2243 URL: https://issues.apache.org/jira/browse/METRON-2243 Project: Metron Issue Type: Improvement Reporter: Shane Ardell After running `npm audit` in both UIs, we have a few dependencies and quite a few nested dependencies needing version updates. This should be as simple as running `npm audit fix`, although there may be a few dependencies needing major version updates that require manual updates. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (METRON-2147) Metron UI localization timezone
[ https://issues.apache.org/jira/browse/METRON-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913482#comment-16913482 ] Shane Ardell commented on METRON-2147: -- I know this ticket came first, but I already opened a PR with the other ticket referenced. > Metron UI localization timezone > --- > > Key: METRON-2147 > URL: https://issues.apache.org/jira/browse/METRON-2147 > Project: Metron > Issue Type: New Feature >Reporter: Donny Lie >Priority: Major > Labels: features > > HCP Metron Alert UI shows GMT timezone but my time is in GMT + 07:00 My > server and all cluster metron node is on local timezone and synchronized with > chronyd I see in Kibana, > timestamp field is correctly shows my timezone, How can I change Metron Alert > UI to my local timezone? > If not existent to change it, please provide it as a new feature? Thanks, > Thanks! Best Regards, *Donny Lie* -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (METRON-2211) [UI] Alerts UI should optionally render timestamp in local time
[ https://issues.apache.org/jira/browse/METRON-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2211: Assignee: Shane Ardell > [UI] Alerts UI should optionally render timestamp in local time > --- > > Key: METRON-2211 > URL: https://issues.apache.org/jira/browse/METRON-2211 > Project: Metron > Issue Type: Improvement >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > Currently, timestamps show in UTC time when the timestamp field is included > as a column header. This could be confusing for a user seeing alerts "from > the future" because their local time is behind UTC time. Even if there is no > confusion, a user might prefer seeing alerts based on their local time vs UTC. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (METRON-2211) [UI] Alerts UI should optionally render timestamp in local time
Shane Ardell created METRON-2211: Summary: [UI] Alerts UI should optionally render timestamp in local time Key: METRON-2211 URL: https://issues.apache.org/jira/browse/METRON-2211 Project: Metron Issue Type: Improvement Reporter: Shane Ardell Currently, timestamps show in UTC time when the timestamp field is included as a column header. This could be confusing for a user seeing alerts "from the future" because their local time is behind UTC time. Even if there is no confusion, a user might prefer seeing alerts based on their local time vs UTC. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (METRON-2208) [UI] Increase unit test coverage for Alert Details
[ https://issues.apache.org/jira/browse/METRON-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2208: Assignee: Shane Ardell > [UI] Increase unit test coverage for Alert Details > -- > > Key: METRON-2208 > URL: https://issues.apache.org/jira/browse/METRON-2208 > Project: Metron > Issue Type: Improvement >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > Our current test coverage for the Alert Details component is around 30% right > now. We should improve this to be above 75% branch coverage. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (METRON-2208) [UI] Increase unit test coverage for Alert Details
Shane Ardell created METRON-2208: Summary: [UI] Increase unit test coverage for Alert Details Key: METRON-2208 URL: https://issues.apache.org/jira/browse/METRON-2208 Project: Metron Issue Type: Improvement Reporter: Shane Ardell Our current test coverage for the Alert Details component is around 30% right now. We should improve this to be above 75% branch coverage. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (METRON-2199) [UI] Add ability to turn off query building in Alerts UI search input
[ https://issues.apache.org/jira/browse/METRON-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2199: Assignee: Shane Ardell > [UI] Add ability to turn off query building in Alerts UI search input > - > > Key: METRON-2199 > URL: https://issues.apache.org/jira/browse/METRON-2199 > Project: Metron > Issue Type: Improvement >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > We should give users the option to turn off the query building feature of the > Alerts UI search input instead of forcing them to use it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (METRON-2199) [UI] Add ability to turn off query building in Alerts UI search input
Shane Ardell created METRON-2199: Summary: [UI] Add ability to turn off query building in Alerts UI search input Key: METRON-2199 URL: https://issues.apache.org/jira/browse/METRON-2199 Project: Metron Issue Type: Improvement Reporter: Shane Ardell We should give users the option to turn off the query building feature of the Alerts UI search input instead of forcing them to use it. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (METRON-2184) Intermittent travis failure in restGetShouldTimeoutWithSuppliedTimeout test
Shane Ardell created METRON-2184:
Summary: Intermittent travis failure in
restGetShouldTimeoutWithSuppliedTimeout test
Key: METRON-2184
URL: https://issues.apache.org/jira/browse/METRON-2184
Project: Metron
Issue Type: Improvement
Reporter: Shane Ardell
I had a build on master randomly fail today with the following error:
RestFunctionsIntegrationTest.restGetShouldTimeoutWithSuppliedTimeout:279
expected null, but was:<\{get=success}>
Link to full stack trace here:
[https://travis-ci.org/apache/metron/jobs/559329378]
I saw this ticket from last year and I'm wondering if it's possible the issue
is related:
https://issues.apache.org/jira/browse/METRON-1870?jql=project%20%3D%20METRON%20AND%20text%20~%20%22intermittent%20failure%22
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (METRON-1870) Intermittent Stellar REST test failures
[
https://issues.apache.org/jira/browse/METRON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886141#comment-16886141
]
Shane Ardell commented on METRON-1870:
--
It looks like we are still getting this error intermittently. This is from the
build of master today:
[https://travis-ci.org/apache/metron/jobs/559329378#L8129]
> Intermittent Stellar REST test failures
> ---
>
> Key: METRON-1870
> URL: https://issues.apache.org/jira/browse/METRON-1870
> Project: Metron
> Issue Type: Bug
>Reporter: Ryan Merriman
>Assignee: Ryan Merriman
>Priority: Major
> Fix For: 0.7.0
>
>
> There have been a few intermittent travis failures reported for the Stellar
> RestGet function:
> restGetShouldTimeoutWithSuppliedTimeout(org.apache.metron.stellar.dsl.functions.RestFunctionsTest)
> Time elapsed: 0.336 sec <<< ERROR!
> org.apache.metron.stellar.dsl.ParseException: Unable to parse:
> REST_GET('http://localhost:41396/get', \{ "timeout": 1 } ) due to: Connection
> is not open
> and:
> restGetShouldHandleIOException(org.apache.metron.stellar.dsl.functions.RestFunctionsTest)
> Time elapsed: 0.314 sec <<< FAILURE! java.lang.AssertionError: expected
> null, but was:<\{get=success}>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (METRON-2183) Update to Angular v7
[ https://issues.apache.org/jira/browse/METRON-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2183: Assignee: Shane Ardell > Update to Angular v7 > > > Key: METRON-2183 > URL: https://issues.apache.org/jira/browse/METRON-2183 > Project: Metron > Issue Type: Improvement >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Long term support for Angular v6 will end in November this year, so we should > update what version we use. [Per the suggestion of the Angular > team|https://angular.io/guide/releases#supported-update-paths], we should > update to version 7 before updating to 8. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (METRON-2179) [UI] Make navigation in both UIs consistent
[ https://issues.apache.org/jira/browse/METRON-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2179: Assignee: Shane Ardell > [UI] Make navigation in both UIs consistent > --- > > Key: METRON-2179 > URL: https://issues.apache.org/jira/browse/METRON-2179 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Time Spent: 2.5h > Remaining Estimate: 0h > > Currently, both UIs approach navigation in two different ways. This makes the > interfaces seem inconsistent and can be confusing for new users. Both ways > are also not collapsible. We also cannot navigate between both UIs (this was > intentional in the original implementation, but feedback from users over time > seems to indicate separating the personas is not necessarily beneficial). > We should either build a reusable component or use a navigation component > from an external library to keep things consistent between both UIs. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (METRON-2174) [UI] Grouped alerts total can differ from search alerts total
[ https://issues.apache.org/jira/browse/METRON-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2174: Assignee: Shane Ardell > [UI] Grouped alerts total can differ from search alerts total > - > > Key: METRON-2174 > URL: https://issues.apache.org/jira/browse/METRON-2174 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Attachments: Screen Shot 2017-10-09 at 4.34.37 PM.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Originally mentioned in this ticket: > https://issues.apache.org/jira/browse/METRON-1242 > In the Alerts UI, when a user searches and then filters by a group or groups, > the total amount of grouped alerts can differ from the total amount of alerts > from the search. See screenshot for a visual description. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (METRON-2183) Update to Angular v7
Shane Ardell created METRON-2183: Summary: Update to Angular v7 Key: METRON-2183 URL: https://issues.apache.org/jira/browse/METRON-2183 Project: Metron Issue Type: Improvement Reporter: Shane Ardell Long term support for Angular v6 will end in November this year, so we should update what version we use. [Per the suggestion of the Angular team|https://angular.io/guide/releases#supported-update-paths], we should update to version 7 before updating to 8. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (METRON-2179) [UI] Make navigation in both UIs consistent
Shane Ardell created METRON-2179: Summary: [UI] Make navigation in both UIs consistent Key: METRON-2179 URL: https://issues.apache.org/jira/browse/METRON-2179 Project: Metron Issue Type: Bug Reporter: Shane Ardell Currently, both UIs approach navigation in two different ways. This makes the interfaces seem inconsistent and can be confusing for new users. Both ways are also not collapsible. We also cannot navigate between both UIs (this was intentional in the original implementation, but feedback from users over time seems to indicate separating the personas is not necessarily beneficial). We should either build a reusable component or use a navigation component from an external library to keep things consistent between both UIs. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (METRON-2174) [UI] Grouped alerts total can differ from search alerts total
[ https://issues.apache.org/jira/browse/METRON-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2174: - Description: Originally mentioned in this ticket: https://issues.apache.org/jira/browse/METRON-1242 In the Alerts UI, when a user searches and then filters by a group or groups, the total amount of grouped alerts can differ from the total amount of alerts from the search. See screenshot for a visual description. was: Originally mentioned in this ticket: https://issues.apache.org/jira/browse/METRON-1242 When a user searches and then filters by a group or groups, the total amount of grouped alerts can differ from the total amount of alerts from the search. See screenshot for a visual description. > [UI] Grouped alerts total can differ from search alerts total > - > > Key: METRON-2174 > URL: https://issues.apache.org/jira/browse/METRON-2174 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > Attachments: Screen Shot 2017-10-09 at 4.34.37 PM.png > > > Originally mentioned in this ticket: > https://issues.apache.org/jira/browse/METRON-1242 > In the Alerts UI, when a user searches and then filters by a group or groups, > the total amount of grouped alerts can differ from the total amount of alerts > from the search. See screenshot for a visual description. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2174) [UI] Grouped alerts total can differ from search alerts total
Shane Ardell created METRON-2174: Summary: [UI] Grouped alerts total can differ from search alerts total Key: METRON-2174 URL: https://issues.apache.org/jira/browse/METRON-2174 Project: Metron Issue Type: Bug Reporter: Shane Ardell Attachments: Screen Shot 2017-10-09 at 4.34.37 PM.png Originally mentioned in this ticket: https://issues.apache.org/jira/browse/METRON-1242 When a user searches and then filters by a group or groups, the total amount of grouped alerts can differ from the total amount of alerts from the search. See screenshot for a visual description. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2161: Assignee: Shane Ardell > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Attachments: long-message-bug.png, saved-searches-bug.gif, > search-arrow-bug.png > > Time Spent: 10m > Remaining Estimate: 0h > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). > See attached images and gif for details. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Description: * Position of the arrow in the Alerts UI search bar seem misaligned and too close to text. * Long message notifications will overlap the close button in both Alerts and Management UI. * Saved searches panel is opening awkwardly on the right (should open from the left). See attached images and gif for details. was: * Position of the arrow in the Alerts UI search bar seem misaligned and too close to text. * Long message notifications will overlap the close button in both Alerts and Management UI. * Saved searches panel is opening awkwardly on the right (should open from the left). > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > Attachments: long-message-bug.png, saved-searches-bug.gif, > search-arrow-bug.png > > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). > See attached images and gif for details. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Description: * Position of the arrow in the Alerts UI search bar seem misaligned and too close to text. * Long message notifications will overlap the close button in both Alerts and Management UI. * Saved searches panel is opening awkwardly on the right (should open from the left). was: * Position of the arrow in the Alerts UI search bar seem misaligned and too close to text. * Long message notifications will overlap the close button in both Alerts and Management UI. * Saved searches panel is opening awkwardly on the right (should open from the left). > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > Attachments: long-message-bug.png, saved-searches-bug.gif, > search-arrow-bug.png > > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Attachment: search-arrow-bug.png > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > Attachments: long-message-bug.png, saved-searches-bug.gif, > search-arrow-bug.png > > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Attachment: saved-searches-bug.gif > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > Attachments: long-message-bug.png, saved-searches-bug.gif, > search-arrow-bug.png > > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Attachment: long-message-bug.png > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > Attachments: long-message-bug.png, saved-searches-bug.gif, > search-arrow-bug.png > > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Attachment: long-message-bug.png > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Attachment: (was: saved-searches-bug.gif) > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Attachment: (was: search-arrow-original.png) > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Attachment: search-arrow-original.png > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Attachment: saved-searches-bug.gif > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Attachment: (was: long-message-bug.png) > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Summary: [UI] CSS positioning bugs in Alerts and MGMT UI (was: [UI]CSS positioning bugs in Alerts and MGMT UI) > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI]CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Summary: [UI]CSS positioning bugs in Alerts and MGMT UI (was: Fix a few CSS positioning bugs) > [UI]CSS positioning bugs in Alerts and MGMT UI > -- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2161) [UI] CSS positioning bugs in Alerts and MGMT UI
[ https://issues.apache.org/jira/browse/METRON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-2161: - Description: * Position of the arrow in the Alerts UI search bar seem misaligned and too close to text. * Long message notifications will overlap the close button in both Alerts and Management UI. * Saved searches panel is opening awkwardly on the right (should open from the left). > [UI] CSS positioning bugs in Alerts and MGMT UI > --- > > Key: METRON-2161 > URL: https://issues.apache.org/jira/browse/METRON-2161 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > > * Position of the arrow in the Alerts UI search bar seem misaligned and too > close to text. > * Long message notifications will overlap the close button in both Alerts > and Management UI. > * Saved searches panel is opening awkwardly on the right (should open from > the left). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2161) Fix a few CSS positioning bugs
Shane Ardell created METRON-2161: Summary: Fix a few CSS positioning bugs Key: METRON-2161 URL: https://issues.apache.org/jira/browse/METRON-2161 Project: Metron Issue Type: Bug Reporter: Shane Ardell -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2146) [UI] Datepicker open/close functionality should be more user friendly
Shane Ardell created METRON-2146: Summary: [UI] Datepicker open/close functionality should be more user friendly Key: METRON-2146 URL: https://issues.apache.org/jira/browse/METRON-2146 Project: Metron Issue Type: Bug Reporter: Shane Ardell Attachments: image-2019-05-29-07-54-53-043.png, image-2019-05-29-07-55-04-489.png There are a couple of user-unfriendly behaviors related to the datepicker in the Alerts UI that should be addressed: * If a user double-clicks the datepicker input, pastes a date and then clicks outside the datepicker, the calendar quickly opens and closes. Besides it being unnecessary for the calendar to open if a user is manually adding a timestamp, a user could accidentally click on the calendar and unintentionally select a date. * The calendar only opens if a user clicks on the input. This differs from most datepickers in libraries like Angular Material, which toggle the calendar view by clicking on the calendar icon. I've included a gif of the behavior I'm talking about in the first issue, as well as a gif of how Angular Material's datepicker behaves for reference. !image-2019-05-29-07-54-53-043.png! !image-2019-05-29-07-55-04-489.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-2126) [UI] Editing parser aggregate updates
[ https://issues.apache.org/jira/browse/METRON-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2126: Assignee: Shane Ardell > [UI] Editing parser aggregate updates > - > > Key: METRON-2126 > URL: https://issues.apache.org/jira/browse/METRON-2126 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > We should integrate existing Save based synchronization method with the > Apply/Discard. > Two different kinds of saving like immediate save on edit/creating sensor > mixed with the Apply/Discard on editing/creating aggregates would be both > confusing for the user and hard to maintain. > Elements changed by Edit has to be marked as dirty just like elements changed > by grouping. > Change the save button copy to 'done'. > Ensure the 'name' field is not editable in this mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2126) [UI] Editing parser aggregate updates
Shane Ardell created METRON-2126: Summary: [UI] Editing parser aggregate updates Key: METRON-2126 URL: https://issues.apache.org/jira/browse/METRON-2126 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell We should integrate existing Save based synchronization method with the Apply/Discard. Two different kinds of saving like immediate save on edit/creating sensor mixed with the Apply/Discard on editing/creating aggregates would be both confusing for the user and hard to maintain. Elements changed by Edit has to be marked as dirty just like elements changed by grouping. Change the save button copy to 'done'. Ensure the 'name' field is not editable in this mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-2125) [UI] Making changes visible in the parser list by marking changed items
[ https://issues.apache.org/jira/browse/METRON-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2125: Assignee: Shane Ardell > [UI] Making changes visible in the parser list by marking changed items > --- > > Key: METRON-2125 > URL: https://issues.apache.org/jira/browse/METRON-2125 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > We need to add visual styling to parsers when they are in a changed state but > before those changes have been submitted to be persisted on the server. For > example, when we create a new parser, when we create a new group, when we add > or remove a parser from a group, or when we delete a parser or group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2125) [UI] Making changes visible in the parser list by marking changed items
Shane Ardell created METRON-2125: Summary: [UI] Making changes visible in the parser list by marking changed items Key: METRON-2125 URL: https://issues.apache.org/jira/browse/METRON-2125 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell We need to add visual styling to parsers when they are in a changed state but before those changes have been submitted to be persisted on the server. For example, when we create a new parser, when we create a new group, when we add or remove a parser from a group, or when we delete a parser or group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-2124) [UI] Move status information and start/stop to the Aggregate level
[ https://issues.apache.org/jira/browse/METRON-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2124: Assignee: Shane Ardell > [UI] Move status information and start/stop to the Aggregate level > -- > > Key: METRON-2124 > URL: https://issues.apache.org/jira/browse/METRON-2124 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > When parsers are grouped, we want to be able to start/stop from the aggregate > level. This means hiding individual parser controls when they are grouped, > controlling multiple parsers with a single set of controls for a group, and > displaying status information as a group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2124) [UI] Move status information and start/stop to the Aggregate level
Shane Ardell created METRON-2124: Summary: [UI] Move status information and start/stop to the Aggregate level Key: METRON-2124 URL: https://issues.apache.org/jira/browse/METRON-2124 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell When parsers are grouped, we want to be able to start/stop from the aggregate level. This means hiding individual parser controls when they are grouped, controlling multiple parsers with a single set of controls for a group, and displaying status information as a group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2110) Setup Parser Grouping Service with Mock Backend
Shane Ardell created METRON-2110: Summary: Setup Parser Grouping Service with Mock Backend Key: METRON-2110 URL: https://issues.apache.org/jira/browse/METRON-2110 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell In order to communicate with REST services, we need to setup a service in Angular to make calls. However, since the endpoints won't be exposed until after we are done developing the UI, we must make calls to a mock backend. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2108) Add Drag and Drop Capability to Parsers
Shane Ardell created METRON-2108: Summary: Add Drag and Drop Capability to Parsers Key: METRON-2108 URL: https://issues.apache.org/jira/browse/METRON-2108 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell A user should have the capability to drag a parser onto another parser and create a group from the two parsers. There should be some sort of anchor for the user to use for drag and drop so they can still click on the parser elsewhere to open the details panel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Description: The capability to group parsers via the CLI already exists in Metron, but it currently is not possible to do so through the Management UI. This feature seems important as it allows users to pass in groups of parsers to start, stop, disable and enable rather than enacting the action on each individual parser. An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the REST endpoint work was performed by Ryan Merriman in PR 1396: [https://github.com/apache/metron/pull/1396]. Here is a brief description of the UI changes we proposing (and subsequently implemented in PR 1360). In order to create a parser group, simply drag and drop two parsers together. A user can optionally update the name and add a description before creating the group. Notice that once a group is created, the parser group is highlighted in green and the parsers moved inside of a group are highlighted in yellow. !create-parser-group.gif|width=601,height=330! Once a user has created the parser groups they want, they can simply click on the apply button at the bottom of the screen. You'll notice the highlighting colors go away, a success message appears and controls for all the parsers in the group are available at the group level (in this case the start button). !save-parser-group.gif|width=601,height=330! If a user wants to add to a group or create a new group from nested parsers, they can choose to either merge or create a new group as shown below. !merge-and-create-new-group.gif|width=601,height=330! If a user wants to delete a group, they can simply click on the trash can icon in the group's controls section. We chose to keep the confirmation popup in addition to the apply button in order to prevent accidental group deletions and prevent sending multiple http delete calls one after the other to the backend. If a user decides not to delete a group after confirming with the modal window, they can click on the discard button to return to the previous state. !delete-parser-group.gif|width=601,height=330! was: The capability to group parsers via the CLI already exists in Metron, but it currently is not possible to do so through the Management UI. This feature seems important as it allows users to pass in groups of parsers to start, stop, disable and enable rather than enacting the action on each individual parser. An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the REST endpoint work was performed by Ryan Merriman in PR 1396: [https://github.com/apache/metron/pull/1396]. Here is a brief description of the UI changes. In order to create a parser group, simply drag and drop two parsers together. A user can optionally update the name and add a description before creating the group. Notice that once a group is created, the parser group is highlighted in green and the parsers moved inside of a group are highlighted in yellow. !create-parser-group.gif|width=601,height=330! Once a user has created the parser groups they want, they can simply click on the apply button at the bottom of the screen. You'll notice the highlighting colors go away, a success message appears and controls for all the parsers in the group are available at the group level (in this case the start button). !save-parser-group.gif|width=601,height=330! If a user wants to add to a group or create a new group from nested parsers, they can choose to either merge or create a new group as shown below. !merge-and-create-new-group.gif|width=601,height=330! If a user wants to delete a group, they can simply click on the trash can icon in the group's controls section. We chose to keep the confirmation popup in addition to the apply button in order to prevent accidental group deletions and prevent sending multiple http delete calls one after the other to the backend. If a user decides not to delete a group after confirming with the modal window, they can click on the discard button to return to the previous state. !delete-parser-group.gif|width=601,height=330! > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif, delete-parser-group.gif, > merge-and-create-new-group.gif, save-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Description: The capability to group parsers via the CLI already exists in Metron, but it currently is not possible to do so through the Management UI. This feature seems important as it allows users to pass in groups of parsers to start, stop, disable and enable rather than enacting the action on each individual parser. An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the REST endpoint work was performed by Ryan Merriman in PR 1396: [https://github.com/apache/metron/pull/1396]. Here is a brief description of the UI changes. In order to create a parser group, simply drag and drop two parsers together. A user can optionally update the name and add a description before creating the group. Notice that once a group is created, the parser group is highlighted in green and the parsers moved inside of a group are highlighted in yellow. !create-parser-group.gif|width=601,height=330! Once a user has created the parser groups they want, they can simply click on the apply button at the bottom of the screen. You'll notice the highlighting colors go away, a success message appears and controls for all the parsers in the group are available at the group level (in this case the start button). !save-parser-group.gif|width=601,height=330! If a user wants to add to a group or create a new group from nested parsers, they can choose to either merge or create a new group as shown below. !merge-and-create-new-group.gif|width=601,height=330! If a user wants to delete a group, they can simply click on the trash can icon in the group's controls section. We chose to keep the confirmation popup in addition to the apply button in order to prevent accidental group deletions and prevent sending multiple http delete calls one after the other to the backend. If a user decides not to delete a group after confirming with the modal window, they can click on the discard button to return to the previous state. !delete-parser-group.gif|width=601,height=330! was: The capability to group parsers via the CLI already exists in Metron, but it currently is not possible to do so through the Management UI. This feature seems important as it allows users to pass in groups of parsers to start, stop, disable and enable rather than enacting the action on each individual parser. An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the REST endpoint work was performed by Ryan Merriman in PR 1396: [https://github.com/apache/metron/pull/1396]. Here is a brief description of the UI changes. In order to create a parser group, simply drag and drop two parsers together. A user can optionally update the name and add a description before creating the group. Notice that once a group is created, the parser group is highlighted in green and the parsers moved inside of a group are highlighted in yellow. !create-parser-group.gif|width=601,height=330! Once a user has created the parser groups they want, they can simply click on the apply button at the bottom of the screen. You'll notice the highlighting colors go away, a success message appears and controls for all the parsers in the group are available at the group level (in this case the start button). !save-parser-group.gif|width=601,height=330! If a user wants to delete a group, they can simply click on the trash can icon in the group's controls section. We chose to keep the confirmation popup in addition to the apply button in order to prevent accidental group deletions and prevent sending multiple http delete calls one after the other to the backend. If a user decides not to delete a group after confirming with the modal window, they can click on the discard button to return to the previous state. > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif, delete-parser-group.gif, > merge-and-create-new-group.gif, save-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the CLI already exists in Metron, but it > currently is not possible to do so through the Management UI. This feature > seems important as it allows users to pass in groups of parsers to start, > stop, disable and enable rather than enacting the action on each individual > parser. > An initial
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Attachment: merge-and-create-new-group.gif > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif, delete-parser-group.gif, > merge-and-create-new-group.gif, save-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the CLI already exists in Metron, but it > currently is not possible to do so through the Management UI. This feature > seems important as it allows users to pass in groups of parsers to start, > stop, disable and enable rather than enacting the action on each individual > parser. > An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and > myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the > REST endpoint work was performed by Ryan Merriman in PR 1396: > [https://github.com/apache/metron/pull/1396]. > Here is a brief description of the UI changes. > In order to create a parser group, simply drag and drop two parsers together. > A user can optionally update the name and add a description before creating > the group. Notice that once a group is created, the parser group is > highlighted in green and the parsers moved inside of a group are highlighted > in yellow. > !create-parser-group.gif|width=601,height=330! > Once a user has created the parser groups they want, they can simply click on > the apply button at the bottom of the screen. You'll notice the highlighting > colors go away, a success message appears and controls for all the parsers in > the group are available at the group level (in this case the start button). > !save-parser-group.gif|width=601,height=330! > If a user wants to delete a group, they can simply click on the trash can > icon in the group's controls section. We chose to keep the confirmation popup > in addition to the apply button in order to prevent accidental group > deletions and prevent sending multiple http delete calls one after the other > to the backend. If a user decides not to delete a group after confirming with > the modal window, they can click on the discard button to return to the > previous state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Attachment: delete-parser-group.gif > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif, delete-parser-group.gif, > merge-and-create-new-group.gif, save-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the CLI already exists in Metron, but it > currently is not possible to do so through the Management UI. This feature > seems important as it allows users to pass in groups of parsers to start, > stop, disable and enable rather than enacting the action on each individual > parser. > An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and > myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the > REST endpoint work was performed by Ryan Merriman in PR 1396: > [https://github.com/apache/metron/pull/1396]. > Here is a brief description of the UI changes. > In order to create a parser group, simply drag and drop two parsers together. > A user can optionally update the name and add a description before creating > the group. Notice that once a group is created, the parser group is > highlighted in green and the parsers moved inside of a group are highlighted > in yellow. > !create-parser-group.gif|width=601,height=330! > Once a user has created the parser groups they want, they can simply click on > the apply button at the bottom of the screen. You'll notice the highlighting > colors go away, a success message appears and controls for all the parsers in > the group are available at the group level (in this case the start button). > !save-parser-group.gif|width=601,height=330! > If a user wants to delete a group, they can simply click on the trash can > icon in the group's controls section. We chose to keep the confirmation popup > in addition to the apply button in order to prevent accidental group > deletions and prevent sending multiple http delete calls one after the other > to the backend. If a user decides not to delete a group after confirming with > the modal window, they can click on the discard button to return to the > previous state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Attachment: save-parser-group.gif > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif, save-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the CLI already exists in Metron, but it > currently is not possible to do so through the Management UI. This feature > seems important as it allows users to pass in groups of parsers to start, > stop, disable and enable rather than enacting the action on each individual > parser. > An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and > myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the > REST endpoint work was performed by Ryan Merriman in PR 1396: > [https://github.com/apache/metron/pull/1396]. > Here is a brief description of the UI changes. > In order to create a parser group, simply drag and drop two parsers together. > You can optionally update the name and add a description before creating the > group. > !create-parser-group.gif|width=601,height=330! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Description: The capability to group parsers via the CLI already exists in Metron, but it currently is not possible to do so through the Management UI. This feature seems important as it allows users to pass in groups of parsers to start, stop, disable and enable rather than enacting the action on each individual parser. An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the REST endpoint work was performed by Ryan Merriman in PR 1396: [https://github.com/apache/metron/pull/1396]. Here is a brief description of the UI changes. In order to create a parser group, simply drag and drop two parsers together. You can optionally update the name and add a description before creating the group. !create-parser-group.gif|width=601,height=330! > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the CLI already exists in Metron, but it > currently is not possible to do so through the Management UI. This feature > seems important as it allows users to pass in groups of parsers to start, > stop, disable and enable rather than enacting the action on each individual > parser. > An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and > myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the > REST endpoint work was performed by Ryan Merriman in PR 1396: > [https://github.com/apache/metron/pull/1396]. > Here is a brief description of the UI changes. > In order to create a parser group, simply drag and drop two parsers together. > You can optionally update the name and add a description before creating the > group. > !create-parser-group.gif|width=601,height=330! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Attachment: create-parser-group.gif > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2063) Prevent focused statements from being left in front-end tests
Shane Ardell created METRON-2063: Summary: Prevent focused statements from being left in front-end tests Key: METRON-2063 URL: https://issues.apache.org/jira/browse/METRON-2063 Project: Metron Issue Type: Improvement Reporter: Shane Ardell Focused statements are incredibly handy when creating and debugging unit tests. However, they sometimes find their way into our code, as seen here: https://github.com/apache/metron/pull/1372 We should think about adding a linter rule or possibly a 3rd party plugin to fail the build if a focused statement committed to code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-2059) Downgrade Cypress version back to non-failing version
[ https://issues.apache.org/jira/browse/METRON-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2059: Assignee: Shane Ardell > Downgrade Cypress version back to non-failing version > - > > Key: METRON-2059 > URL: https://issues.apache.org/jira/browse/METRON-2059 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > We currently have an intermittent failure happening in Travis stemming from > yauzl, the unzipping tool used by Cypress. The issue is currently open in > their issues and can be found here: > https://github.com/cypress-io/cypress/issues/3515 > According to some feedback on that linked issue, some have had luck > downgrading the version of Cypress to 3.1.0. We should downgrade and test > with multiple builds to try to resolve this issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2059) Downgrade Cypress version back to non-failing version
Shane Ardell created METRON-2059: Summary: Downgrade Cypress version back to non-failing version Key: METRON-2059 URL: https://issues.apache.org/jira/browse/METRON-2059 Project: Metron Issue Type: Bug Reporter: Shane Ardell We currently have an intermittent failure happening in Travis stemming from yauzl, the unzipping tool used by Cypress. The issue is currently open in their issues and can be found here: https://github.com/cypress-io/cypress/issues/3515 According to some feedback on that linked issue, some have had luck downgrading the version of Cypress to 3.1.0. We should downgrade and test with multiple builds to try to resolve this issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2029) Configure Table should have filter
Shane Ardell created METRON-2029: Summary: Configure Table should have filter Key: METRON-2029 URL: https://issues.apache.org/jira/browse/METRON-2029 Project: Metron Issue Type: Improvement Reporter: Shane Ardell Currently, when a user opens the configure table panel, they must scroll down to see all their choices. This list can be really long, so it would be beneficial to have an input for a user to type into and have the options filtered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1987) Upgrade Alert UI to stable Bootstrap 4
[ https://issues.apache.org/jira/browse/METRON-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1987: - Description: Like we did for the Management UI, we should upgrade the version of Bootstrap that we are using to the latest stable version. We are currently on an alpha version which includes deprecated class names and values. > Upgrade Alert UI to stable Bootstrap 4 > -- > > Key: METRON-1987 > URL: https://issues.apache.org/jira/browse/METRON-1987 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > > Like we did for the Management UI, we should upgrade the version of Bootstrap > that we are using to the latest stable version. We are currently on an alpha > version which includes deprecated class names and values. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1987) Upgrade Alert UI to stable Bootstrap 4
Shane Ardell created METRON-1987: Summary: Upgrade Alert UI to stable Bootstrap 4 Key: METRON-1987 URL: https://issues.apache.org/jira/browse/METRON-1987 Project: Metron Issue Type: Bug Reporter: Shane Ardell -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1971) Short timeout value in Cypress may cause build failures
Shane Ardell created METRON-1971: Summary: Short timeout value in Cypress may cause build failures Key: METRON-1971 URL: https://issues.apache.org/jira/browse/METRON-1971 Project: Metron Issue Type: Bug Reporter: Shane Ardell According to the Cypress docs, it is unnecessary to add a wait command after cy.visit. "Waiting for this is unnecessary because the cy.visit() resolves once the page fires its load event. By that time all of your assets have been loaded including javascript, stylesheets, and html." However, the problem is with an Angular application, the page firing a load event does not mean that the entire view has rendered yet. In systems where memory is scarce, such as a Travis environment or a machine that has memory-intensive applications running, this means a page load can take a few seconds (or possibly even longer). We currently use the default timeout in Cypress, which is only 4000ms. I believe this short timeout can cause failures like this in Metron: https://travis-ci.org/apache/metron/jobs/483945575 We should increase the defaultCommandTimeout in cypress.json to something like 3ms or greater to prevent failures like this in the future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1900) Migrate tests from Alert Filters spec
[ https://issues.apache.org/jira/browse/METRON-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1900: Assignee: Shane Ardell > Migrate tests from Alert Filters spec > - > > Key: METRON-1900 > URL: https://issues.apache.org/jira/browse/METRON-1900 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > *Filtering alerts* > (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) > *Existing tests to migrate:* > * Display facets data > * Search when facet is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1900) Migrate tests from Alert Filters spec
[ https://issues.apache.org/jira/browse/METRON-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1900: Assignee: Tamas Fodor (was: Shane Ardell) > Migrate tests from Alert Filters spec > - > > Key: METRON-1900 > URL: https://issues.apache.org/jira/browse/METRON-1900 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tamas Fodor >Priority: Major > > *Filtering alerts* > (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) > *Existing tests to migrate:* > * Display facets data > * Search when facet is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1899) Migrate and add tests from Alert Details Status spec
[ https://issues.apache.org/jira/browse/METRON-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1899: Assignee: Shane Ardell > Migrate and add tests from Alert Details Status spec > > > Key: METRON-1899 > URL: https://issues.apache.org/jira/browse/METRON-1899 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > *__**Alert details pane* > > (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) > *Existing tests to move:* > * Changing alert statuses > * Adding comment for table view > * Adding comment for tree view > *Scenarios to add:* > * Deleting comment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1907) Migrate tests from Alerts List spec
[ https://issues.apache.org/jira/browse/METRON-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1907: Assignee: Tamas Fodor > Migrate tests from Alerts List spec > --- > > Key: METRON-1907 > URL: https://issues.apache.org/jira/browse/METRON-1907 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tamas Fodor >Priority: Major > > *Alert list* > (metron-alerts/e2e/alerts-list/alerts-list.e2e-spec.ts) > *Existing tests to migrate:* > * should have all the UI elements > * should have all pagination controls and they should be working > * should have all settings controls and they should be working > * play pause should start polling and stop polling > * should select columns from table configuration > * should have all time-range controls > * should have all time range values populated - 1 > * should have all time range values populated - 2 > * should have all time range values populated - 3 > * should have all time range values populated - 4 > * should disable date picker when timestamp is present in search > * should have now included when to date is empty > * should have all time-range included while searching -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1958) Optimize Cypress to use best practices
[ https://issues.apache.org/jira/browse/METRON-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1958: Assignee: Shane Ardell > Optimize Cypress to use best practices > -- > > Key: METRON-1958 > URL: https://issues.apache.org/jira/browse/METRON-1958 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > As of recent, there have been multiple unpredictable Cypress failures in > Travis. While looking into these failures, I noticed a few anti-patterns we > have in place that could definitely cause these failures: > 1) We currently run `ng serve --aot` as a test server for Cypress. We are > running this command in parallel with the command that starts Cypress. As you > could imagine, this presents a race condition where Cypress could start > running before the server starts. Instead of using Angular CLI to build and > serve our project for Cypress to test against, we should first build the > project, then serve the built project with the Express server we have in > place already. Serving an already built project with Express is so fast we > should be able to confidently run it in parallel with the Cypress test script > and not worry about any race conditions failing our tests. This is the > standard practice that has been shown in other Angular/Cypress test examples. > 2) Per the Cypress team's best practice recommendations, [we should remove > the command to logout in the afterEach > hook|https://docs.cypress.io/guides/references/best-practices.html#Using-after-or-afterEach-hooks] > since it's unnecessary for our needs and may be the cause for our failures > regarding the logout link. > 3) Again per the Cypress team's best practices, [we should set a baseUrl in > our cypress.json config > file|https://docs.cypress.io/guides/references/best-practices.html#Setting-a-global-baseUrl]. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1903) Migrate tests from Meta Alerts spec
[ https://issues.apache.org/jira/browse/METRON-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1903: Assignee: Tamas Fodor > Migrate tests from Meta Alerts spec > --- > > Key: METRON-1903 > URL: https://issues.apache.org/jira/browse/METRON-1903 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tamas Fodor >Priority: Major > > *Meta Alerts* > (metron-alerts/e2e/alerts-list/meta-alerts/meta-alert.e2e-spec.ts) > *Existing tests to migrate:* > * should have all the steps for meta alerts workflow > * should create a meta alert from nesting of more than one level > * remove meta alerts -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1905) Migrate tests from Table View spec
[ https://issues.apache.org/jira/browse/METRON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1905: Assignee: Tibor Meller > Migrate tests from Table View spec > -- > > Key: METRON-1905 > URL: https://issues.apache.org/jira/browse/METRON-1905 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tibor Meller >Priority: Major > > *Alerts table view* > (metron-alerts/e2e/alerts-list/table-view/table-view.e2e-spec.ts) > *Existing tests to migrate:* > * sorting ASC by ip_src_addr > * sorting DESC by ip_src_addr > * sorting ASC by Score > * sorting DESC by Score -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1901) Migrate tests from Alert List Status spec
[ https://issues.apache.org/jira/browse/METRON-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1901: Assignee: Tamas Fodor > Migrate tests from Alert List Status spec > - > > Key: METRON-1901 > URL: https://issues.apache.org/jira/browse/METRON-1901 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tamas Fodor >Priority: Major > > *Alert item status change on the list and tree view* > (metron-alerts/e2e/alerts-list/alert-status/alerts-list-status.e2e-spec.ts) > *Existing tests to migrate:* > * change alert status for multiple alerts to OPEN > * change alert status for multiple alerts to DISMISS > * change alert status for multiple alerts to ESCALATE > * change alert status for multiple alerts to RESOLVE > * change alert status for multiple alerts to OPEN in tree view > * change alert status for multiple alerts to DISMISS in tree view > * change alert status for multiple alerts to ESCALATE in tree view > * change alert status for multiple alerts to RESOLVE in tree view -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1902) Migrate tests from Configure Table spec
[ https://issues.apache.org/jira/browse/METRON-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1902: Assignee: Tibor Meller > Migrate tests from Configure Table spec > --- > > Key: METRON-1902 > URL: https://issues.apache.org/jira/browse/METRON-1902 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tibor Meller >Priority: Major > > *Configure table view* > (metron-alerts/e2e/alerts-list/configure-table/configure-table.e2e-spec.ts) > *Existing tests to migrate:* > * select columns from table configuration > * rename columns from table configuration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1930) Update webpack-dev-server in Alerts UI
[ https://issues.apache.org/jira/browse/METRON-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1930: Assignee: Shane Ardell > Update webpack-dev-server in Alerts UI > -- > > Key: METRON-1930 > URL: https://issues.apache.org/jira/browse/METRON-1930 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Attachments: Screen Shot 2018-12-10 at 4.46.33 PM.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > After running `npm audit` in the Alerts UI, it looks like we need to update > our version of webpack-dev-server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1906) Migrate tests from Tree View spec
[ https://issues.apache.org/jira/browse/METRON-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1906: Assignee: Shane Ardell > Migrate tests from Tree View spec > - > > Key: METRON-1906 > URL: https://issues.apache.org/jira/browse/METRON-1906 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > *Alerts tree view* > (metron-alerts/e2e/alerts-list/tree-view/tree-view.e2e-spec.ts) > *Existing tests to migrate:* > * should have all group by elements > * drag and drop should change group order > * should have group details for single group by > * should have group details for multiple group by > * should have sort working for group details for multiple sub groups > * should have search working for group details for multiple sub groups -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1908) Migrate alerts from Login spec
[ https://issues.apache.org/jira/browse/METRON-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1908: Assignee: Shane Ardell > Migrate alerts from Login spec > -- > > Key: METRON-1908 > URL: https://issues.apache.org/jira/browse/METRON-1908 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > *Login* > (metron-alerts/e2e/login/login.e2e-spec.ts) > *Existing alerts to migrate:* > * should display error message for invalid credentials > * should login for valid credentials > * should logout -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1959) Ensure server starts before Cypress
Shane Ardell created METRON-1959: Summary: Ensure server starts before Cypress Key: METRON-1959 URL: https://issues.apache.org/jira/browse/METRON-1959 Project: Metron Issue Type: Bug Reporter: Shane Ardell Per the Cypress team's recommendation, we should be using the `wait-on` or `start-server-and-test` packages to ensure our server starts before Cypress runs and prevent a possible race condition. https://docs.cypress.io/guides/guides/continuous-integration.html#Boot-your-server -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1958) Optimize Cypress to use best practices
Shane Ardell created METRON-1958: Summary: Optimize Cypress to use best practices Key: METRON-1958 URL: https://issues.apache.org/jira/browse/METRON-1958 Project: Metron Issue Type: Bug Reporter: Shane Ardell As of recent, there have been multiple unpredictable Cypress failures in Travis. While looking into these failures, I noticed a few anti-patterns we have in place that could definitely cause these failures: 1) We currently run `ng serve --aot` as a test server for Cypress. We are running this command in parallel with the command that starts Cypress. As you could imagine, this presents a race condition where Cypress could start running before the server starts. Instead of using Angular CLI to build and serve our project for Cypress to test against, we should first build the project, then serve the built project with the Express server we have in place already. Serving an already built project with Express is so fast we should be able to confidently run it in parallel with the Cypress test script and not worry about any race conditions failing our tests. This is the standard practice that has been shown in other Angular/Cypress test examples. 2) Per the Cypress team's best practice recommendations, [we should remove the command to logout in the afterEach hook|https://docs.cypress.io/guides/references/best-practices.html#Using-after-or-afterEach-hooks] since it's unnecessary for our needs and may be the cause for our failures regarding the logout link. 3) Again per the Cypress team's best practices, [we should set a baseUrl in our cypress.json config file|https://docs.cypress.io/guides/references/best-practices.html#Setting-a-global-baseUrl]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1936) Cypress fails when trying to parse double quotes
Shane Ardell created METRON-1936: Summary: Cypress fails when trying to parse double quotes Key: METRON-1936 URL: https://issues.apache.org/jira/browse/METRON-1936 Project: Metron Issue Type: Bug Reporter: Shane Ardell Double quotes that are used inside the parser list component are causing a parsing issue for Cypress, even if you switch them out with html encoded double quotes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1930) Update webpack-dev-server in Alerts UI
Shane Ardell created METRON-1930: Summary: Update webpack-dev-server in Alerts UI Key: METRON-1930 URL: https://issues.apache.org/jira/browse/METRON-1930 Project: Metron Issue Type: Bug Reporter: Shane Ardell Attachments: Screen Shot 2018-12-10 at 4.46.33 PM.png After running `npm audit` in the Alerts UI, it looks like we need to update our version of webpack-dev-server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1903) Migrate tests from Meta Alerts spec
Shane Ardell created METRON-1903: Summary: Migrate tests from Meta Alerts spec Key: METRON-1903 URL: https://issues.apache.org/jira/browse/METRON-1903 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Meta Alerts* (metron-alerts/e2e/alerts-list/meta-alerts/meta-alert.e2e-spec.ts) *Existing tests to migrate:* * should have all the steps for meta alerts workflow * should create a meta alert from nesting of more than one level * remove meta alerts -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1906) Migrate tests from Tree View spec
Shane Ardell created METRON-1906: Summary: Migrate tests from Tree View spec Key: METRON-1906 URL: https://issues.apache.org/jira/browse/METRON-1906 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Alerts tree view* (metron-alerts/e2e/alerts-list/tree-view/tree-view.e2e-spec.ts) *Existing tests to migrate:* * should have all group by elements * drag and drop should change group order * should have group details for single group by * should have group details for multiple group by * should have sort working for group details for multiple sub groups * should have search working for group details for multiple sub groups -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1905) Migrate tests from Table View spec
Shane Ardell created METRON-1905: Summary: Migrate tests from Table View spec Key: METRON-1905 URL: https://issues.apache.org/jira/browse/METRON-1905 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Alerts table view* (metron-alerts/e2e/alerts-list/table-view/table-view.e2e-spec.ts) *Existing tests to migrate:* * sorting ASC by ip_src_addr * sorting DESC by ip_src_addr * sorting ASC by Score * sorting DESC by Score -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1904) Migrate tests from Save Search spec
Shane Ardell created METRON-1904: Summary: Migrate tests from Save Search spec Key: METRON-1904 URL: https://issues.apache.org/jira/browse/METRON-1904 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Search and save search* (metron-alerts/e2e/alerts-list/save-search/save-search.e2e-spec.ts) *Existing tests to migrate:* * should display all the default values for saved searches * should have all save search controls and they save search should be working * should delete search items from search box * should delete first search items from search box having multiple search fields * manually entering search queries to search box and pressing enter key should search -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1902) Migrate tests from Configure Table spec
Shane Ardell created METRON-1902: Summary: Migrate tests from Configure Table spec Key: METRON-1902 URL: https://issues.apache.org/jira/browse/METRON-1902 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Configure table view* (metron-alerts/e2e/alerts-list/configure-table/configure-table.e2e-spec.ts) *Existing tests to migrate:* * select columns from table configuration * rename columns from table configuration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1899) Migrate and add tests from Alert Details Status spec
[ https://issues.apache.org/jira/browse/METRON-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1899: - Description: *__**Alert details pane* (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) *Existing tests to move:* * Changing alert statuses * Adding comment for table view * Adding comment for tree view *Scenarios to add:* * Deleting comment was: Alert details pane (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) *Existing tests to move:* * Changing alert statuses * Adding comment for table view * Adding comment for tree view *Scenarios to add:* * Deleting comment > Migrate and add tests from Alert Details Status spec > > > Key: METRON-1899 > URL: https://issues.apache.org/jira/browse/METRON-1899 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Priority: Major > > *__**Alert details pane* > > (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) > *Existing tests to move:* > * Changing alert statuses > * Adding comment for table view > * Adding comment for tree view > *Scenarios to add:* > * Deleting comment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1900) Migrate tests from Alert Filters spec
[ https://issues.apache.org/jira/browse/METRON-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1900: - Description: *Filtering alerts* (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) *Existing tests to migrate:* * Display facets data * Search when facet is selected was: Filtering alerts (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) *Existing tests to migrate:* * Display facets data * Search when facet is selected > Migrate tests from Alert Filters spec > - > > Key: METRON-1900 > URL: https://issues.apache.org/jira/browse/METRON-1900 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Priority: Major > > *Filtering alerts* > (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) > *Existing tests to migrate:* > * Display facets data > * Search when facet is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
