[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used#242275
Merged
cnasikas merged 4 commits intoelastic:mainfrom Nov 11, 2025
Conversation
umbopepato
added
release_note:fix
Team:ResponseOps
…ts-table-pagination-resetting
Contributor
|
Pinging @elastic/response-ops (Team:ResponseOps) |
ersin-erdal
approved these changes
Nov 10, 2025
Contributor
ersin-erdal
left a comment
ersin-erdal
left a comment
There was a problem hiding this comment.
LGTM,
Tested locally, works as expected.
Member
|
@elasticmachine merge upstream |
Contributor
|
Starting backport for target branches: 8.19, 9.1, 9.2 |
Contributor
💚 Build Succeeded
Metrics [docs]Async chunks
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
|
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Nov 11, 2025
…ReloadRequestTime is used (elastic#242275) ## 📄 Summary Removes the `refresh` callback from the `lastReloadRequestTime` effect dependencies to avoid triggering a refresh when the refresh callback itself changes (like it happened [here](elastic#241593)). <details> <summary> ## 🧪 Verification steps </summary> 1. Create a rule that fires many alerts (i.e. Security query rule) 2. Wait for the alerts to be generated 3. Navigate to the rule page from Stack Management > Rules 4. Check that the pagination in the alerts table at the bottom of the page works correctly </details> ## ⏪ Backport rationale Backporting to all open versions since this is a bug fix ## Release Notes Fixes a bug that caused the alerts tables pagination to be stuck in the Rule pages ## 🔗 References Fixes elastic#241593 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] ~~Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~ - [ ] ~~[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 - [ ] ~~If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~ - [ ] ~~This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations.~~ - [ ] ~~[Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed~~ - [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. --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 722c33e)
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
Member
Author
Handling the conflicts asap |
kibanamachine
added a commit
that referenced
this pull request
Nov 11, 2025
…n lastReloadRequestTime is used (#242275) (#242527) # Backport This will backport the following commits from `main` to `9.2`: - [[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275)](#242275) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-11-11T11:44:29Z","message":"[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275)\n\n## 📄 Summary\n\nRemoves the `refresh` callback from the `lastReloadRequestTime` effect\ndependencies to avoid triggering a refresh when the refresh callback\nitself changes (like it happened\n[here](https://github.com/elastic/kibana/issues/241593)).\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create a rule that fires many alerts (i.e. Security query rule)\n2. Wait for the alerts to be generated\n3. Navigate to the rule page from Stack Management > Rules\n4. Check that the pagination in the alerts table at the bottom of the\npage works correctly\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all open versions since this is a bug fix\n\n## Release Notes\n\nFixes a bug that caused the alerts tables pagination to be stuck in the\nRule pages\n\n## 🔗 References\n\nFixes #241593\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\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- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\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.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"722c33eb42562a86412be79e745ea4702f36a6d7","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","backport:version","v9.3.0","v8.19.7","v9.1.7","v9.2.1"],"title":"[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used","number":242275,"url":"https://github.com/elastic/kibana/pull/242275","mergeCommit":{"message":"[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275)\n\n## 📄 Summary\n\nRemoves the `refresh` callback from the `lastReloadRequestTime` effect\ndependencies to avoid triggering a refresh when the refresh callback\nitself changes (like it happened\n[here](https://github.com/elastic/kibana/issues/241593)).\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create a rule that fires many alerts (i.e. Security query rule)\n2. Wait for the alerts to be generated\n3. Navigate to the rule page from Stack Management > Rules\n4. Check that the pagination in the alerts table at the bottom of the\npage works correctly\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all open versions since this is a bug fix\n\n## Release Notes\n\nFixes a bug that caused the alerts tables pagination to be stuck in the\nRule pages\n\n## 🔗 References\n\nFixes #241593\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\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- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\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.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"722c33eb42562a86412be79e745ea4702f36a6d7"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.1","9.2"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/242275","number":242275,"mergeCommit":{"message":"[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275)\n\n## 📄 Summary\n\nRemoves the `refresh` callback from the `lastReloadRequestTime` effect\ndependencies to avoid triggering a refresh when the refresh callback\nitself changes (like it happened\n[here](https://github.com/elastic/kibana/issues/241593)).\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create a rule that fires many alerts (i.e. Security query rule)\n2. Wait for the alerts to be generated\n3. Navigate to the rule page from Stack Management > Rules\n4. Check that the pagination in the alerts table at the bottom of the\npage works correctly\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all open versions since this is a bug fix\n\n## Release Notes\n\nFixes a bug that caused the alerts tables pagination to be stuck in the\nRule pages\n\n## 🔗 References\n\nFixes #241593\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\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- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\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.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"722c33eb42562a86412be79e745ea4702f36a6d7"}},{"branch":"8.19","label":"v8.19.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
umbopepato
added a commit
to umbopepato/kibana
that referenced
this pull request
Nov 11, 2025
…ReloadRequestTime is used (elastic#242275) ## 📄 Summary Removes the `refresh` callback from the `lastReloadRequestTime` effect dependencies to avoid triggering a refresh when the refresh callback itself changes (like it happened [here](elastic#241593)). <details> <summary> ## 🧪 Verification steps </summary> 1. Create a rule that fires many alerts (i.e. Security query rule) 2. Wait for the alerts to be generated 3. Navigate to the rule page from Stack Management > Rules 4. Check that the pagination in the alerts table at the bottom of the page works correctly </details> ## ⏪ Backport rationale Backporting to all open versions since this is a bug fix ## Release Notes Fixes a bug that caused the alerts tables pagination to be stuck in the Rule pages ## 🔗 References Fixes elastic#241593 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] ~~Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~ - [ ] ~~[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 - [ ] ~~If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~ - [ ] ~~This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations.~~ - [ ] ~~[Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed~~ - [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. --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 722c33e) # Conflicts: # src/platform/packages/shared/response-ops/alerts-table/components/alerts_table.test.tsx
Member
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
umbopepato
added a commit
to umbopepato/kibana
that referenced
this pull request
Nov 11, 2025
…ReloadRequestTime is used (elastic#242275) ## 📄 Summary Removes the `refresh` callback from the `lastReloadRequestTime` effect dependencies to avoid triggering a refresh when the refresh callback itself changes (like it happened [here](elastic#241593)). <details> <summary> ## 🧪 Verification steps </summary> 1. Create a rule that fires many alerts (i.e. Security query rule) 2. Wait for the alerts to be generated 3. Navigate to the rule page from Stack Management > Rules 4. Check that the pagination in the alerts table at the bottom of the page works correctly </details> ## ⏪ Backport rationale Backporting to all open versions since this is a bug fix ## Release Notes Fixes a bug that caused the alerts tables pagination to be stuck in the Rule pages ## 🔗 References Fixes elastic#241593 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] ~~Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~ - [ ] ~~[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 - [ ] ~~If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~ - [ ] ~~This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations.~~ - [ ] ~~[Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed~~ - [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. --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 722c33e) # Conflicts: # src/platform/packages/shared/response-ops/alerts-table/components/alerts_table.test.tsx
umbopepato
added a commit
that referenced
this pull request
Nov 11, 2025
…n lastReloadRequestTime is used (#242275) (#242563) # Backport This will backport the following commits from `main` to `9.1`: - [[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275)](#242275) <!--- Backport version: 10.1.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-11-11T11:44:29Z","message":"[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275)\n\n## 📄 Summary\n\nRemoves the `refresh` callback from the `lastReloadRequestTime` effect\ndependencies to avoid triggering a refresh when the refresh callback\nitself changes (like it happened\n[here](https://github.com/elastic/kibana/issues/241593)).\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create a rule that fires many alerts (i.e. Security query rule)\n2. Wait for the alerts to be generated\n3. Navigate to the rule page from Stack Management > Rules\n4. Check that the pagination in the alerts table at the bottom of the\npage works correctly\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all open versions since this is a bug fix\n\n## Release Notes\n\nFixes a bug that caused the alerts tables pagination to be stuck in the\nRule pages\n\n## 🔗 References\n\nFixes #241593\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\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- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\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.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"722c33eb42562a86412be79e745ea4702f36a6d7","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","backport:version","v9.3.0","v8.19.7","v9.1.7","v9.2.1"],"title":"[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used","number":242275,"url":"https://github.com/elastic/kibana/pull/242275","mergeCommit":{"message":"[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275)\n\n## 📄 Summary\n\nRemoves the `refresh` callback from the `lastReloadRequestTime` effect\ndependencies to avoid triggering a refresh when the refresh callback\nitself changes (like it happened\n[here](https://github.com/elastic/kibana/issues/241593)).\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create a rule that fires many alerts (i.e. Security query rule)\n2. Wait for the alerts to be generated\n3. Navigate to the rule page from Stack Management > Rules\n4. Check that the pagination in the alerts table at the bottom of the\npage works correctly\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all open versions since this is a bug fix\n\n## Release Notes\n\nFixes a bug that caused the alerts tables pagination to be stuck in the\nRule pages\n\n## 🔗 References\n\nFixes #241593\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\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- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\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.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"722c33eb42562a86412be79e745ea4702f36a6d7"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.1"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/242275","number":242275,"mergeCommit":{"message":"[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275)\n\n## 📄 Summary\n\nRemoves the `refresh` callback from the `lastReloadRequestTime` effect\ndependencies to avoid triggering a refresh when the refresh callback\nitself changes (like it happened\n[here](https://github.com/elastic/kibana/issues/241593)).\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create a rule that fires many alerts (i.e. Security query rule)\n2. Wait for the alerts to be generated\n3. Navigate to the rule page from Stack Management > Rules\n4. Check that the pagination in the alerts table at the bottom of the\npage works correctly\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all open versions since this is a bug fix\n\n## Release Notes\n\nFixes a bug that caused the alerts tables pagination to be stuck in the\nRule pages\n\n## 🔗 References\n\nFixes #241593\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\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- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\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.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"722c33eb42562a86412be79e745ea4702f36a6d7"}},{"branch":"8.19","label":"v8.19.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/242527","number":242527,"state":"MERGED","mergeCommit":{"sha":"11cbc3a21cad0cf26355a31a92e02343a0ca76e0","message":"[9.2] [ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275) (#242527)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.2`:\n- [[ResponseOps][Alerts] Fix alerts table pagination resetting when\nlastReloadRequestTime is used\n(#242275)](https://github.com/elastic/kibana/pull/242275)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>"}}]}] BACKPORT-->
umbopepato
added a commit
that referenced
this pull request
Nov 13, 2025
…en lastReloadRequestTime is used (#242275) (#242564) # Backport This will backport the following commits from `main` to `8.19`: - [[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275)](#242275) <!--- Backport version: 10.1.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-11-11T11:44:29Z","message":"[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275)\n\n## 📄 Summary\n\nRemoves the `refresh` callback from the `lastReloadRequestTime` effect\ndependencies to avoid triggering a refresh when the refresh callback\nitself changes (like it happened\n[here](https://github.com/elastic/kibana/issues/241593)).\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create a rule that fires many alerts (i.e. Security query rule)\n2. Wait for the alerts to be generated\n3. Navigate to the rule page from Stack Management > Rules\n4. Check that the pagination in the alerts table at the bottom of the\npage works correctly\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all open versions since this is a bug fix\n\n## Release Notes\n\nFixes a bug that caused the alerts tables pagination to be stuck in the\nRule pages\n\n## 🔗 References\n\nFixes #241593\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\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- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\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.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"722c33eb42562a86412be79e745ea4702f36a6d7","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","backport:version","v9.3.0","v8.19.7","v9.1.7","v9.2.1"],"title":"[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used","number":242275,"url":"https://github.com/elastic/kibana/pull/242275","mergeCommit":{"message":"[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275)\n\n## 📄 Summary\n\nRemoves the `refresh` callback from the `lastReloadRequestTime` effect\ndependencies to avoid triggering a refresh when the refresh callback\nitself changes (like it happened\n[here](https://github.com/elastic/kibana/issues/241593)).\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create a rule that fires many alerts (i.e. Security query rule)\n2. Wait for the alerts to be generated\n3. Navigate to the rule page from Stack Management > Rules\n4. Check that the pagination in the alerts table at the bottom of the\npage works correctly\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all open versions since this is a bug fix\n\n## Release Notes\n\nFixes a bug that caused the alerts tables pagination to be stuck in the\nRule pages\n\n## 🔗 References\n\nFixes #241593\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\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- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\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.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"722c33eb42562a86412be79e745ea4702f36a6d7"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.1"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/242275","number":242275,"mergeCommit":{"message":"[ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275)\n\n## 📄 Summary\n\nRemoves the `refresh` callback from the `lastReloadRequestTime` effect\ndependencies to avoid triggering a refresh when the refresh callback\nitself changes (like it happened\n[here](https://github.com/elastic/kibana/issues/241593)).\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create a rule that fires many alerts (i.e. Security query rule)\n2. Wait for the alerts to be generated\n3. Navigate to the rule page from Stack Management > Rules\n4. Check that the pagination in the alerts table at the bottom of the\npage works correctly\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all open versions since this is a bug fix\n\n## Release Notes\n\nFixes a bug that caused the alerts tables pagination to be stuck in the\nRule pages\n\n## 🔗 References\n\nFixes #241593\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\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- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\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.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"722c33eb42562a86412be79e745ea4702f36a6d7"}},{"branch":"8.19","label":"v8.19.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/242527","number":242527,"state":"MERGED","mergeCommit":{"sha":"11cbc3a21cad0cf26355a31a92e02343a0ca76e0","message":"[9.2] [ResponseOps][Alerts] Fix alerts table pagination resetting when lastReloadRequestTime is used (#242275) (#242527)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.2`:\n- [[ResponseOps][Alerts] Fix alerts table pagination resetting when\nlastReloadRequestTime is used\n(#242275)](https://github.com/elastic/kibana/pull/242275)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>"}}]}] BACKPORT-->
eokoneyo
pushed a commit
to eokoneyo/kibana
that referenced
this pull request
Dec 2, 2025
…ReloadRequestTime is used (elastic#242275) ## 📄 Summary Removes the `refresh` callback from the `lastReloadRequestTime` effect dependencies to avoid triggering a refresh when the refresh callback itself changes (like it happened [here](elastic#241593)). <details> <summary> ## 🧪 Verification steps </summary> 1. Create a rule that fires many alerts (i.e. Security query rule) 2. Wait for the alerts to be generated 3. Navigate to the rule page from Stack Management > Rules 4. Check that the pagination in the alerts table at the bottom of the page works correctly </details> ## ⏪ Backport rationale Backporting to all open versions since this is a bug fix ## Release Notes Fixes a bug that caused the alerts tables pagination to be stuck in the Rule pages ## 🔗 References Fixes elastic#241593 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] ~~Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~ - [ ] ~~[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 - [ ] ~~If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~ - [ ] ~~This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations.~~ - [ ] ~~[Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed~~ - [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. --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
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
6 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
Removes the
refreshcallback from thelastReloadRequestTimeeffect dependencies to avoid triggering a refresh when the refresh callback itself changes (like it happened here).🧪 Verification steps
⏪ Backport rationale
Backporting to all open versions since this is a bug fix
Release Notes
Fixes a bug that caused the alerts tables pagination to be stuck in the Rule pages
🔗 References
Fixes #241593
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n supportDocumentation was added for features that require explanation or tutorialsIf a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker listThis was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. Therelease_note:breakinglabel should be applied in these situations.Flaky Test Runner was used on any tests changedrelease_note:*label is applied per the guidelinesbackport:*labels.