You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
Risk
Probability
Severity
Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.
Low
High
Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.
High
Low
Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.
Medium
High
Unit tests will verify that any feature flag or plugin combination still results in our service operational.
[job][logs] OSS Accessibility Tests / a11y tests using flights sample data Dashboard create dashboard button
[job][logs] Default CI Group #10 / Actions and Triggers app Home page Loads the app Loads the Alerts page
[job][logs] Default CI Group #10 / Actions and Triggers app Home page Loads the app with limited privileges Loads the Alerts page
[job][logs] Default CI Group #2 / Advanced Settings security feature controls global advanced_settings all privileges "before all" hook for "shows management navlink"
[job][logs] Default CI Group #13 / Grok Debugger App Grok Debugger "before all" hook for "Loads the app"
[job][logs] Default CI Group #13 / Grok Debugger App Grok Debugger "before all" hook for "Loads the app"
[job][logs] Default CI Group #15 / machine learning permissions for user with full ML access with data loaded (ft_ml_poweruser_spaces) should display elements on ML Overview page correctly
[job][logs] Default CI Group #15 / machine learning permissions for user with full ML access with no data loaded (ft_ml_poweruser) "before all" hook for "should display the ML entry in Kibana app menu"
[job][logs] Default CI Group #2 / Reporting Functional Tests with Security enabled Security with reporting_user built-in role Dashboard: Download CSV file does not allow user that does not have reporting privileges
[job][logs] Jest Tests #3 / rolesManagementApp mount() works for the clone role page
[job][logs] Jest Tests #3 / rolesManagementApp mount() works for the create role page
[job][logs] Jest Tests #3 / rolesManagementApp mount() works for the edit role page
[job][logs] OSS CI Group #7 / saved objects management saved objects relationships flyout displays the invalid references
[job][logs] Default CI Group #21 / transform permissions for user with full transform access with no data loaded "before all" hook for "should display elements in the Transform list page correctly"
Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.
Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Summarize your PR. If it involves visual changes include a screenshot or gif.
Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers