[Cases] Update total event in ES document when attaching an event#247996
Merged
christineweng merged 1 commit intoelastic:mainfrom Jan 7, 2026
Merged
[Cases] Update total event in ES document when attaching an event#247996christineweng merged 1 commit intoelastic:mainfrom
christineweng merged 1 commit intoelastic:mainfrom
Conversation
christineweng
added
release_note:fix
backport:version
Contributor
|
Pinging @elastic/kibana-cases (Team:Cases) |
christineweng
force-pushed
the
cases-fix-total-event-update
branch
from
96e9d4d to
764588a
Compare
Contributor
💔 Build Failed
Failed CI StepsMetrics [docs]
History |
Contributor
|
Starting backport for target branches: 9.2, 9.3 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jan 7, 2026
…astic#247996) ## Summary Ref: elastic#245916 How to test: - Create a case and attach some alerts and events - Go to Discover, create a data view called Cases, with pattern `.kibana_alerting_cases*` - Verify the stats are populated correctly ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [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 - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. (cherry picked from commit 03e8ae8)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jan 7, 2026
…astic#247996) ## Summary Ref: elastic#245916 How to test: - Create a case and attach some alerts and events - Go to Discover, create a data view called Cases, with pattern `.kibana_alerting_cases*` - Verify the stats are populated correctly ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [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 - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. (cherry picked from commit 03e8ae8)
Contributor
💚 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
Jan 7, 2026
…nt (#247996) (#248133) # Backport This will backport the following commits from `main` to `9.2`: - [[Cases] Update total event in ES document when attaching an event (#247996)](#247996) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-01-07T16:39:40Z","message":"[Cases] Update total event in ES document when attaching an event (#247996)\n\n## Summary\n\nRef: https://github.com/elastic/kibana/issues/245916\n\nHow to test:\n- Create a case and attach some alerts and events\n- Go to Discover, create a data view called Cases, with pattern\n`.kibana_alerting_cases*`\n- Verify the stats are populated correctly\n\n### Checklist\n\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"03e8ae8dbbae5700cf7fe89ee77853a4ebd8b201","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:version","Team:Cases","v9.3.0","v9.4.0","v9.2.4"],"title":"[Cases] Update total event in ES document when attaching an event","number":247996,"url":"https://github.com/elastic/kibana/pull/247996","mergeCommit":{"message":"[Cases] Update total event in ES document when attaching an event (#247996)\n\n## Summary\n\nRef: https://github.com/elastic/kibana/issues/245916\n\nHow to test:\n- Create a case and attach some alerts and events\n- Go to Discover, create a data view called Cases, with pattern\n`.kibana_alerting_cases*`\n- Verify the stats are populated correctly\n\n### Checklist\n\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"03e8ae8dbbae5700cf7fe89ee77853a4ebd8b201"}},"sourceBranch":"main","suggestedTargetBranches":["9.3","9.2"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/247996","number":247996,"mergeCommit":{"message":"[Cases] Update total event in ES document when attaching an event (#247996)\n\n## Summary\n\nRef: https://github.com/elastic/kibana/issues/245916\n\nHow to test:\n- Create a case and attach some alerts and events\n- Go to Discover, create a data view called Cases, with pattern\n`.kibana_alerting_cases*`\n- Verify the stats are populated correctly\n\n### Checklist\n\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"03e8ae8dbbae5700cf7fe89ee77853a4ebd8b201"}},{"branch":"9.2","label":"v9.2.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: christineweng <18648970+christineweng@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Jan 7, 2026
…nt (#247996) (#248134) # Backport This will backport the following commits from `main` to `9.3`: - [[Cases] Update total event in ES document when attaching an event (#247996)](#247996) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-01-07T16:39:40Z","message":"[Cases] Update total event in ES document when attaching an event (#247996)\n\n## Summary\n\nRef: https://github.com/elastic/kibana/issues/245916\n\nHow to test:\n- Create a case and attach some alerts and events\n- Go to Discover, create a data view called Cases, with pattern\n`.kibana_alerting_cases*`\n- Verify the stats are populated correctly\n\n### Checklist\n\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"03e8ae8dbbae5700cf7fe89ee77853a4ebd8b201","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:version","Team:Cases","v9.3.0","v9.4.0","v9.2.4"],"title":"[Cases] Update total event in ES document when attaching an event","number":247996,"url":"https://github.com/elastic/kibana/pull/247996","mergeCommit":{"message":"[Cases] Update total event in ES document when attaching an event (#247996)\n\n## Summary\n\nRef: https://github.com/elastic/kibana/issues/245916\n\nHow to test:\n- Create a case and attach some alerts and events\n- Go to Discover, create a data view called Cases, with pattern\n`.kibana_alerting_cases*`\n- Verify the stats are populated correctly\n\n### Checklist\n\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"03e8ae8dbbae5700cf7fe89ee77853a4ebd8b201"}},"sourceBranch":"main","suggestedTargetBranches":["9.3","9.2"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/247996","number":247996,"mergeCommit":{"message":"[Cases] Update total event in ES document when attaching an event (#247996)\n\n## Summary\n\nRef: https://github.com/elastic/kibana/issues/245916\n\nHow to test:\n- Create a case and attach some alerts and events\n- Go to Discover, create a data view called Cases, with pattern\n`.kibana_alerting_cases*`\n- Verify the stats are populated correctly\n\n### Checklist\n\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"03e8ae8dbbae5700cf7fe89ee77853a4ebd8b201"}},{"branch":"9.2","label":"v9.2.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: christineweng <18648970+christineweng@users.noreply.github.com>
devamanv
pushed a commit
to devamanv/kibana
that referenced
this pull request
Jan 12, 2026
…astic#247996) ## Summary Ref: elastic#245916 How to test: - Create a case and attach some alerts and events - Go to Discover, create a data view called Cases, with pattern `.kibana_alerting_cases*` - Verify the stats are populated correctly ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [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 - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Summary
Ref: #245916
How to test:
.kibana_alerting_cases*Checklist
release_note:*label is applied per the guidelinesbackport:*labels.