[8.19] [Alerting] [Incident Management] Show cases on alert detail overview (#222903) #223962
Conversation
This file contains hidden or 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
…lastic#222903) ## Summary Resolves elastic#221835. Adds case links to the Alert Details status bar. When there is exactly 1 case, the status bar displays that case's name and links to the case detail page. When there is more than 1 case, an additional link with the text `+N cases` will render as well. This link simply sends the user to the Cases overview page. We need improved filtering to allow the URL to pass a series of case IDs to pre-filter the overview page to make the user's landing experience better when using this feature. If there is no linked case, the case links will not display anything. ## TODOS Best not to review this until these are checked off. - [ ] If the user utilizes the _Add to case_ feature of the detail page, the cases shown in the status bar do not update. We should fix this before merging. - [ ] We should also ensure we have additional unit tests included for the locator code 100% coverage, as it's a little tricky. - [ ] We need unit tests for the links hook. ## Testing this PR - Create three alerts. - Do not attach the first one to any cases. Go to the detail page and see that there is no case-related info displayed in the status bar. - Attach the second alert to a case, and go to its detail page. See that the case is shown in the status bar like `Case: {caseName}`. - Attach the third alert to more than one case. Go to the detail page and verify that the two links, `caseName` and `+ N more` are displayed and that they function properly. - Repeat this testing for a kibana with and without a basePath, and across spaces, to ensure the locators are working correctly. <img width="779" alt="image" src="https://github.com/user-attachments/assets/f135bd1e-a0dc-45f2-a003-a375f7589cf0" /> (cherry picked from commit e37e7ad)
3 tasks
botelastic
bot
added
the
Team:actionable-obs
Contributor
|
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
History
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Backport
This will backport the following commits from
mainto8.19:Questions ?
Please refer to the Backport tool documentation