-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs for "Alert User Assignment" feature #4226
Comments
Serverless doc updates:
|
UI copy work being tracked in #4295 |
@e40pud and @yctercero - https://github.com/elastic/staging-serverless-security-docs/pull/232 contains a first draft of the alert assignment feature docs. I'm going to update all the outdated screenshots, add some ones, and finalize the content once I'm back from PTO. cc: @jmikell821 |
…2504) (#170579) ## Summary With this PR we introduce a new Alert User Assignment feature: - It is possible to assign a user/s to alert/s - There is a new "Assignees" column in the alerts table which displays avatars of assigned users - There is a bulk action to update assignees for multiple alerts - It is possible to see and update assignees inside the alert details flyout component - There is an "Assignees" filter button on the Alerts page which allows to filter alerts by assignees We decided to develop this feature on a separate branch. This gives us ability to make sure that it is thoroughly tested and we did not break anything in production. Since there is a data scheme changes involved we decided that it will be a better approach. cc @yctercero ## Testing notes In order to test assignments you need to create a few users. Then for users to appear in user profiles dropdown menu you need to activate them by login into those account at least once. https://github.com/elastic/kibana/assets/2700761/8eeb13f3-2d16-4fba-acdf-755024a59fc2 Main ticket elastic/security-team#2504 ## Bugfixes - [x] elastic/security-team#8028 - [x] elastic/security-team#8034 - [x] elastic/security-team#8006 - [x] elastic/security-team#8025 ## Enhancements - [x] elastic/security-team#8033 ### Checklist - [x] Functional changes are hidden behind a feature flag. If not hidden, the PR explains why these changes are being implemented in a long-living feature branch. - [x] Functional changes are covered with a test plan and automated tests. - [x] #171306 - [x] #171307 - [x] Stability of new and changed tests is verified using the [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner). - [x] https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4091 - [x] Comprehensive manual testing is done by two engineers: the PR author and one of the PR reviewers. Changes are tested in both ESS and Serverless. - [x] Mapping changes are accompanied by a technical design document. It can be a GitHub issue or an RFC explaining the changes. The design document is shared with and approved by the appropriate teams and individual stakeholders. * elastic/security-team#7647 - [x] Functional changes are communicated to the Docs team. A ticket or PR is opened in https://github.com/elastic/security-docs. The following information is included: any feature flags used, affected environments (Serverless, ESS, or both). **NOTE: as discussed we will wait until docs are ready to merge this PR**. * elastic/security-docs#4226 * elastic/staging-serverless-security-docs#232 --------- Co-authored-by: Marshall Main <[email protected]> Co-authored-by: Xavier Mouligneau <[email protected]> Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Sergi Massaneda <[email protected]>
Security solution ticket with detailed feature description https://github.com/elastic/security-team/issues/2504
Description
We need to add documentation for the new alert assignments feature. It is planned to merge changes this or next week.
The key items of the Alert User Assignment feature:
This feature will be available in both ESS and Serverless
280417832-8eeb13f3-2d16-4fba-acdf-755024a59fc2.mov
The text was updated successfully, but these errors were encountered: