[Solution nav] Use flyout for Stack Management in Search and Observability solutions #208632
+167
−29
Conversation
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
tsullivan
force-pushed
the
solution-nav/consistent-stackmanagement-flyout
branch
8 times, most recently
from
b8bc52a to
85100ab
Compare
tsullivan
commented
Jan 31, 2025
| children: [ | ||
| { | ||
| title: i18n.translate('xpack.serverlessObservability.nav.mngt.data', { | ||
| defaultMessage: 'Data', |
There was a problem hiding this comment.
@elastic/kibana-management it looks like this structure has a more official source of truth within the Management plugin, but it is not accessible to outside plugins [1]. Is there a chance we could update the public start contract of the Management plugin so I wouldn't need this declaration? I am worried this information could be missing a critical link, or become out of date.
There was a problem hiding this comment.
@tsullivan I'm sure this can be improved but I think the code is a good representation of the group dynamics that produced it - stateful kibana has a way of expressing management app listing and solutions want to control their own listing completely independent of whatever stateful is doing. We could certainly expose some management content but its unclear to me how this would be helpful.
There was a problem hiding this comment.
Thanks @mattkime. I have recently taken over this code and I wanted to make sure that there isn't an obvious alternative to this implementation that would be better. It sounds like keeping solutions in control of their own listing is what we should keep doing.
stateful kibana has a way of expressing management app listing
It could be pointed out that independent control isn't just an issue for serverless. The Solution Nav is used in stateful deployments when the Space uses a Solution view, and the listing of management apps is completely controlled by the solution there as well. That goes back prior to this PR, though.
tsullivan
force-pushed
the
solution-nav/consistent-stackmanagement-flyout
branch
from
842fea5 to
a780cdd
Compare
tsullivan
commented
Feb 3, 2025
| await solutionNavigation.sidenav.expectLinkActive({ deepLinkId: 'management' }); | ||
| await solutionNavigation.sidenav.clickLink({ navId: 'stack_management' }); | ||
| await solutionNavigation.sidenav.expectLinkActive({ navId: 'stack_management' }); | ||
| await solutionNavigation.sidenav.clickPanelLink('management:tags'); |
There was a problem hiding this comment.
Had to add this, because the breadcrumbs will not say Stack Management unless the user navigates to a management. The Tags app was chosen arbitrarily.
tsullivan
added
release_note:skip
|
Heads up to reviewers, this is a bug fix and will be backported to 8.18 and higher |
2 tasks
mgiota
requested changes
Feb 11, 2025
There was a problem hiding this comment.
@tsullivan Thanks for trying to make the Stack Management experience consistent. I tested it out locally and I noticed a few things that look a bit broken in Observability.
In the Video below you can see how clicking on the four square icon in Security toggles the slide panel. Same behavior should happen for Observability as well, but in your PR it doesn't work that way. Slide panel still stays open if I click on the arrow or the label. I have to click outside to make it close. We want to have it closed, once clicking on the icon or the label.
https://github.com/user-attachments/assets/a482c787-cd63-417d-a432-39a3820182dd
I am linking here the PR where this was implemented. I haven't tested serverless, but my guess is that it should be broken there as well.
You can watch the Video in the PR's description for the desired behavior of Observability navigation experience. In a nutshell things that need to be fixed:
- clicking on the label or right arrow should toggle the slide panel
four squareicon next to Stack Management was replaced with an arrow in your PR. In the linked PR Observability > Stack Management also has the four square and it should stay this way. It looks like a bug to me, unless I am not aware of any new requirements. cc @petrklapka @vinaychandrasekhar.
|
@tsullivan I was reading the Requirements in the github issue and I have a comment regarding this requirement for security solution In the Video below it doesn't look like it works this way. Clicking on Stack Management still opens the landing page. Unless there was a different landing page before and what I see on Security is fine. Can you clarify if this works as expected? Screen.Recording.2025-02-11.at.13.53.49.mov |
tsullivan
changed the title
mgiota
approved these changes
Feb 11, 2025
|
Starting backport for target branches: 8.18, 8.x, 9.0 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 11, 2025
…ility solutions (elastic#208632) ## Summary Closes elastic#208636 Part of elastic/kibana-team#1439 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] New lists of Stack Management navigation items were added for flyout menus in serverless projects using static declarations. There is a risk that these lists have missing items, which could hurt user experience by making the pages harder to navigate to. ### Screenshots <details><summary>Observability / Serverless</summary>  </details> <details><summary>Observability / Stateful</summary>  </details> <details><summary>Search / Serverless</summary>  </details> <details><summary>Search / Stateful</summary>  (cherry picked from commit f164464)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 11, 2025
…ility solutions (elastic#208632) ## Summary Closes elastic#208636 Part of elastic/kibana-team#1439 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] New lists of Stack Management navigation items were added for flyout menus in serverless projects using static declarations. There is a risk that these lists have missing items, which could hurt user experience by making the pages harder to navigate to. ### Screenshots <details><summary>Observability / Serverless</summary>  </details> <details><summary>Observability / Stateful</summary>  </details> <details><summary>Search / Serverless</summary>  </details> <details><summary>Search / Stateful</summary>  (cherry picked from commit f164464)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 11, 2025
…ility solutions (elastic#208632) ## Summary Closes elastic#208636 Part of elastic/kibana-team#1439 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] New lists of Stack Management navigation items were added for flyout menus in serverless projects using static declarations. There is a risk that these lists have missing items, which could hurt user experience by making the pages harder to navigate to. ### Screenshots <details><summary>Observability / Serverless</summary>  </details> <details><summary>Observability / Stateful</summary>  </details> <details><summary>Search / Serverless</summary>  </details> <details><summary>Search / Stateful</summary>  (cherry picked from commit f164464)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Feb 11, 2025
…servability solutions (#208632) (#210631) # Backport This will backport the following commits from `main` to `9.0`: - [[Solution nav] Use flyout for Stack Management in Search and Observability solutions (#208632)](#208632) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tim Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T16:14:32Z","message":"[Solution nav] Use flyout for Stack Management in Search and Observability solutions (#208632)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.\r\n\r\n### Screenshots\r\n<details><summary>Observability / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Observability / Stateful</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Stateful</summary>\r\n\r\n","sha":"f16446486c7695a13f564d53f7d630337a9a50e8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:SharedUX","ci:project-deploy-observability","Team:obs-ux-management","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Solution nav] Use flyout for Stack Management in Search and Observability solutions","number":208632,"url":"https://github.com/elastic/kibana/pull/208632","mergeCommit":{"message":"[Solution nav] Use flyout for Stack Management in Search and Observability solutions (#208632)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.\r\n\r\n### Screenshots\r\n<details><summary>Observability / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Observability / Stateful</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Stateful</summary>\r\n\r\n","sha":"f16446486c7695a13f564d53f7d630337a9a50e8"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208632","number":208632,"mergeCommit":{"message":"[Solution nav] Use flyout for Stack Management in Search and Observability solutions (#208632)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.\r\n\r\n### Screenshots\r\n<details><summary>Observability / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Observability / Stateful</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Stateful</summary>\r\n\r\n","sha":"f16446486c7695a13f564d53f7d630337a9a50e8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>
kapral18
added a commit
to agusruidiazgd/kibana
that referenced
this pull request
Feb 11, 2025
…on-206439 * main: (402 commits) [Search]: Fix Number type field to have correct property (elastic#210462) Change filter for rule monitoring gaps (elastic#209983) Update Logs Explorer deprecation messages (elastic#201307) [APM] Remove `error.id` in `getErrorGroupMainStatistics` query as it's not used (elastic#210613) [Embeddable] Fix presentation panel styles (elastic#210113) [ci] enable Scout reporter for on-merge-unsupported-ftrs (elastic#210627) [Fix][Synonyms UI]Add navigation link to the Detail breadcrumb. (elastic#209574) chore(dep): bump `store2` from `2.12.0` to `2.14.4` (elastic#210530) [scout] adding test helper `@kbn/scout-oblt` package and uptate onboarding tests (elastic#209761) [Cloud Security] Asset Inventory table flyout controls (elastic#208452) [ML] Fix model deployment check in file uploader (elastic#209585) Updates archive again (elastic#209828) [Security Solution] Added concurrency limits and request throttling to prebuilt rule routes (elastic#209551) [Search] [Onboarding] Update search api to use EventEmitter instead of Provider (elastic#209784) [maps] lazy load map actions (elastic#210252) [Cloud Security] Adding telemetry collection condition based on render condition (elastic#208758) [Solution nav] Use flyout for Stack Management in Search and Observability solutions (elastic#208632) [Search] Fix Add Inference Endpoint API call (elastic#210243) [Agentless Connectors] Integration overview panel (elastic#210222) [Lens] Restore dynamic colouring by value for Last value agg (elastic#209110) ...
tsullivan
added a commit
that referenced
this pull request
Feb 11, 2025
…0471) This reverts commit 949d5d1 from #208632 (comment). ## Summary Closes #208636 Part of elastic/kibana-team#1439 </details> <details><summary>Security / Serverless (no longer in this PR)</summary>  </details> <details><summary>Security / Stateful (no longer in this PR)</summary>  </details> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] New lists of Stack Management navigation items were added for flyout menus in serverless projects using static declarations. There is a risk that these lists have missing items, which could hurt user experience by making the pages harder to navigate to.
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 11, 2025
…stic#210471) This reverts commit 949d5d1 from elastic#208632 (comment). ## Summary Closes elastic#208636 Part of elastic/kibana-team#1439 </details> <details><summary>Security / Serverless (no longer in this PR)</summary>  </details> <details><summary>Security / Stateful (no longer in this PR)</summary>  </details> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] New lists of Stack Management navigation items were added for flyout menus in serverless projects using static declarations. There is a risk that these lists have missing items, which could hurt user experience by making the pages harder to navigate to. (cherry picked from commit 145d295)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 11, 2025
…stic#210471) This reverts commit 949d5d1 from elastic#208632 (comment). ## Summary Closes elastic#208636 Part of elastic/kibana-team#1439 </details> <details><summary>Security / Serverless (no longer in this PR)</summary>  </details> <details><summary>Security / Stateful (no longer in this PR)</summary>  </details> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] New lists of Stack Management navigation items were added for flyout menus in serverless projects using static declarations. There is a risk that these lists have missing items, which could hurt user experience by making the pages harder to navigate to. (cherry picked from commit 145d295)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 11, 2025
…stic#210471) This reverts commit 949d5d1 from elastic#208632 (comment). ## Summary Closes elastic#208636 Part of elastic/kibana-team#1439 </details> <details><summary>Security / Serverless (no longer in this PR)</summary>  </details> <details><summary>Security / Stateful (no longer in this PR)</summary>  </details> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] New lists of Stack Management navigation items were added for flyout menus in serverless projects using static declarations. There is a risk that these lists have missing items, which could hurt user experience by making the pages harder to navigate to. (cherry picked from commit 145d295)
kibanamachine
added a commit
that referenced
this pull request
Feb 11, 2025
…bservability solutions (#208632) (#210629) # Backport This will backport the following commits from `main` to `8.18`: - [[Solution nav] Use flyout for Stack Management in Search and Observability solutions (#208632)](#208632) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tim Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T16:14:32Z","message":"[Solution nav] Use flyout for Stack Management in Search and Observability solutions (#208632)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.\r\n\r\n### Screenshots\r\n<details><summary>Observability / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Observability / Stateful</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Stateful</summary>\r\n\r\n","sha":"f16446486c7695a13f564d53f7d630337a9a50e8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:SharedUX","ci:project-deploy-observability","Team:obs-ux-management","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Solution nav] Use flyout for Stack Management in Search and Observability solutions","number":208632,"url":"https://github.com/elastic/kibana/pull/208632","mergeCommit":{"message":"[Solution nav] Use flyout for Stack Management in Search and Observability solutions (#208632)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.\r\n\r\n### Screenshots\r\n<details><summary>Observability / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Observability / Stateful</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Stateful</summary>\r\n\r\n","sha":"f16446486c7695a13f564d53f7d630337a9a50e8"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208632","number":208632,"mergeCommit":{"message":"[Solution nav] Use flyout for Stack Management in Search and Observability solutions (#208632)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.\r\n\r\n### Screenshots\r\n<details><summary>Observability / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Observability / Stateful</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Stateful</summary>\r\n\r\n","sha":"f16446486c7695a13f564d53f7d630337a9a50e8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com> Co-authored-by: Timothy Sullivan <tsullivan@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
Feb 11, 2025
#210471) (#210706) # Backport This will backport the following commits from `main` to `9.0`: - [[Solution nav] Use flyout for Stack management Security Solution (#210471)](#210471) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tim Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T22:04:25Z","message":"[Solution nav] Use flyout for Stack management Security Solution (#210471)\n\nThis reverts commit 949d5d1 from\r\nhttps://github.com//pull/208632#issuecomment-2644086780.\r\n\r\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n</details>\r\n<details><summary>Security / Serverless (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Security / Stateful (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.","sha":"145d295a75e0124a8cc406a67109faef7f05413e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:SharedUX","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Solution nav] Use flyout for Stack management Security Solution","number":210471,"url":"https://github.com/elastic/kibana/pull/210471","mergeCommit":{"message":"[Solution nav] Use flyout for Stack management Security Solution (#210471)\n\nThis reverts commit 949d5d1 from\r\nhttps://github.com//pull/208632#issuecomment-2644086780.\r\n\r\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n</details>\r\n<details><summary>Security / Serverless (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Security / Stateful (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.","sha":"145d295a75e0124a8cc406a67109faef7f05413e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210471","number":210471,"mergeCommit":{"message":"[Solution nav] Use flyout for Stack management Security Solution (#210471)\n\nThis reverts commit 949d5d1 from\r\nhttps://github.com//pull/208632#issuecomment-2644086780.\r\n\r\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n</details>\r\n<details><summary>Security / Serverless (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Security / Stateful (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.","sha":"145d295a75e0124a8cc406a67109faef7f05413e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Feb 11, 2025
…servability solutions (#208632) (#210630) # Backport This will backport the following commits from `main` to `8.x`: - [[Solution nav] Use flyout for Stack Management in Search and Observability solutions (#208632)](#208632) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tim Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T16:14:32Z","message":"[Solution nav] Use flyout for Stack Management in Search and Observability solutions (#208632)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.\r\n\r\n### Screenshots\r\n<details><summary>Observability / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Observability / Stateful</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Stateful</summary>\r\n\r\n","sha":"f16446486c7695a13f564d53f7d630337a9a50e8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:SharedUX","ci:project-deploy-observability","Team:obs-ux-management","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Solution nav] Use flyout for Stack Management in Search and Observability solutions","number":208632,"url":"https://github.com/elastic/kibana/pull/208632","mergeCommit":{"message":"[Solution nav] Use flyout for Stack Management in Search and Observability solutions (#208632)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.\r\n\r\n### Screenshots\r\n<details><summary>Observability / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Observability / Stateful</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Stateful</summary>\r\n\r\n","sha":"f16446486c7695a13f564d53f7d630337a9a50e8"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208632","number":208632,"mergeCommit":{"message":"[Solution nav] Use flyout for Stack Management in Search and Observability solutions (#208632)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.\r\n\r\n### Screenshots\r\n<details><summary>Observability / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Observability / Stateful</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Serverless</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Search / Stateful</summary>\r\n\r\n","sha":"f16446486c7695a13f564d53f7d630337a9a50e8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com> Co-authored-by: Timothy Sullivan <tsullivan@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
Feb 12, 2025
#210471) (#210705) # Backport This will backport the following commits from `main` to `8.x`: - [[Solution nav] Use flyout for Stack management Security Solution (#210471)](#210471) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tim Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T22:04:25Z","message":"[Solution nav] Use flyout for Stack management Security Solution (#210471)\n\nThis reverts commit 949d5d1 from\r\nhttps://github.com//pull/208632#issuecomment-2644086780.\r\n\r\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n</details>\r\n<details><summary>Security / Serverless (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Security / Stateful (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.","sha":"145d295a75e0124a8cc406a67109faef7f05413e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:SharedUX","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Solution nav] Use flyout for Stack management Security Solution","number":210471,"url":"https://github.com/elastic/kibana/pull/210471","mergeCommit":{"message":"[Solution nav] Use flyout for Stack management Security Solution (#210471)\n\nThis reverts commit 949d5d1 from\r\nhttps://github.com//pull/208632#issuecomment-2644086780.\r\n\r\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n</details>\r\n<details><summary>Security / Serverless (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Security / Stateful (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.","sha":"145d295a75e0124a8cc406a67109faef7f05413e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210471","number":210471,"mergeCommit":{"message":"[Solution nav] Use flyout for Stack management Security Solution (#210471)\n\nThis reverts commit 949d5d1 from\r\nhttps://github.com//pull/208632#issuecomment-2644086780.\r\n\r\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n</details>\r\n<details><summary>Security / Serverless (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Security / Stateful (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.","sha":"145d295a75e0124a8cc406a67109faef7f05413e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Feb 12, 2025
…on (#210471) (#210704) # Backport This will backport the following commits from `main` to `8.18`: - [[Solution nav] Use flyout for Stack management Security Solution (#210471)](#210471) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tim Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T22:04:25Z","message":"[Solution nav] Use flyout for Stack management Security Solution (#210471)\n\nThis reverts commit 949d5d1 from\r\nhttps://github.com//pull/208632#issuecomment-2644086780.\r\n\r\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n</details>\r\n<details><summary>Security / Serverless (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Security / Stateful (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.","sha":"145d295a75e0124a8cc406a67109faef7f05413e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:SharedUX","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Solution nav] Use flyout for Stack management Security Solution","number":210471,"url":"https://github.com/elastic/kibana/pull/210471","mergeCommit":{"message":"[Solution nav] Use flyout for Stack management Security Solution (#210471)\n\nThis reverts commit 949d5d1 from\r\nhttps://github.com//pull/208632#issuecomment-2644086780.\r\n\r\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n</details>\r\n<details><summary>Security / Serverless (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Security / Stateful (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.","sha":"145d295a75e0124a8cc406a67109faef7f05413e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210471","number":210471,"mergeCommit":{"message":"[Solution nav] Use flyout for Stack management Security Solution (#210471)\n\nThis reverts commit 949d5d1 from\r\nhttps://github.com//pull/208632#issuecomment-2644086780.\r\n\r\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/208636\r\nPart of https://github.com/elastic/kibana-team/issues/1439\r\n\r\n</details>\r\n<details><summary>Security / Serverless (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n<details><summary>Security / Stateful (no longer in this PR)</summary>\r\n\r\n\r\n\r\n</details>\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] New lists of Stack Management navigation items were added for\r\nflyout menus in serverless projects using static declarations. There is\r\na risk that these lists have missing items, which could hurt user\r\nexperience by making the pages harder to navigate to.","sha":"145d295a75e0124a8cc406a67109faef7f05413e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Closes #208636
Part of https://github.com/elastic/kibana-team/issues/1439
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.
Screenshots
Observability / Serverless
Observability / Stateful
Search / Serverless
Search / Stateful