[Observability Alerting] Refetch alert detail rule data on edit flyout submit#222118
Conversation
|
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
…0.1` to `2.0.2` (elastic#223589) Bump `brace-expansion` from `1.1.11` to `1.11.12` and `2.0.1` to `2.0.2`.
|
Pinging @elastic/obs-ai-assistant (Team:Obs AI Assistant) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
55aed86 to
da60f4a
Compare
💛 Build succeeded, but was flaky
Failed CI StepsTest FailuresMetrics [docs]Async chunks
History
|
|
Starting backport for target branches: 8.19 https://github.com/elastic/kibana/actions/runs/15642933162 |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
…t submit (elastic#222118) ## Summary Resolves elastic#221428. We noticed recently when we added the Investigation Guide that, if the user edits the values in the guide using the edit flyout, the data on the main page will not refresh when they submit. This patch would add an `onUpdate` handler prop to the Header Actions component that would enable it to trigger the refresh on the parent component when the user submits the form in the edit flyout. Example: 
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
3 similar comments
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
…t submit (elastic#222118) ## Summary Resolves elastic#221428. We noticed recently when we added the Investigation Guide that, if the user edits the values in the guide using the edit flyout, the data on the main page will not refresh when they submit. This patch would add an `onUpdate` handler prop to the Header Actions component that would enable it to trigger the refresh on the parent component when the user submits the form in the edit flyout. Example:  (cherry picked from commit 1886697)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…t flyout submit (#222118) (#225131) # Backport This will backport the following commits from `main` to `8.19`: - [[Observability Alerting] Refetch alert detail rule data on edit flyout submit (#222118)](#222118) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Justin Kambic","email":"jk@elastic.co"},"sourceCommit":{"committedDate":"2025-06-13T19:58:44Z","message":"[Observability Alerting] Refetch alert detail rule data on edit flyout submit (#222118)\n\n## Summary\n\nResolves #221428.\n\nWe noticed recently when we added the Investigation Guide that, if the\nuser edits the values in the guide using the edit flyout, the data on\nthe main page will not refresh when they submit.\n\nThis patch would add an `onUpdate` handler prop to the Header Actions\ncomponent that would enable it to trigger the refresh on the parent\ncomponent when the user submits the form in the edit flyout.\n\nExample:\n\n\n","sha":"188669773e9cc1981b5e89f24afcfdc379ad3058","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport missing","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","author:obs-ux-management"],"title":"[Observability Alerting] Refetch alert detail rule data on edit flyout submit","number":222118,"url":"https://github.com/elastic/kibana/pull/222118","mergeCommit":{"message":"[Observability Alerting] Refetch alert detail rule data on edit flyout submit (#222118)\n\n## Summary\n\nResolves #221428.\n\nWe noticed recently when we added the Investigation Guide that, if the\nuser edits the values in the guide using the edit flyout, the data on\nthe main page will not refresh when they submit.\n\nThis patch would add an `onUpdate` handler prop to the Header Actions\ncomponent that would enable it to trigger the refresh on the parent\ncomponent when the user submits the form in the edit flyout.\n\nExample:\n\n\n","sha":"188669773e9cc1981b5e89f24afcfdc379ad3058"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222118","number":222118,"mergeCommit":{"message":"[Observability Alerting] Refetch alert detail rule data on edit flyout submit (#222118)\n\n## Summary\n\nResolves #221428.\n\nWe noticed recently when we added the Investigation Guide that, if the\nuser edits the values in the guide using the edit flyout, the data on\nthe main page will not refresh when they submit.\n\nThis patch would add an `onUpdate` handler prop to the Header Actions\ncomponent that would enable it to trigger the refresh on the parent\ncomponent when the user submits the form in the edit flyout.\n\nExample:\n\n\n","sha":"188669773e9cc1981b5e89f24afcfdc379ad3058"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
Summary
Resolves #221428.
We noticed recently when we added the Investigation Guide that, if the user edits the values in the guide using the edit flyout, the data on the main page will not refresh when they submit.
This patch would add an
onUpdatehandler prop to the Header Actions component that would enable it to trigger the refresh on the parent component when the user submits the form in the edit flyout.Example: