[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer#236724
Merged
KodeRad merged 4 commits intoelastic:mainfrom Sep 30, 2025
Conversation
KodeRad
added
bug
Contributor
|
Pinging @elastic/ml-ui (:ml) |
Contributor
💚 Build Succeeded
Metrics [docs]Async chunks
History
cc @KodeRad |
Contributor
|
Starting backport for target branches: 8.18, 8.19, 9.0, 9.1 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 30, 2025
…hange in Single Metric Viewer (elastic#236724) ## Summary Fixes elastic#224882 This PR: 1. Explicitly resets the value of showForecastCheckbox [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854) Also, it resets the value to default on `fullRestore` [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446) Previously `showForecastCheckbox` value was lingering after we switched the job. 2. Adds `announceOnMount` to satisfy linter (a11y) [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057) [[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238) https://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31 ### 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 37bc98a)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 30, 2025
…hange in Single Metric Viewer (elastic#236724) ## Summary Fixes elastic#224882 This PR: 1. Explicitly resets the value of showForecastCheckbox [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854) Also, it resets the value to default on `fullRestore` [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446) Previously `showForecastCheckbox` value was lingering after we switched the job. 2. Adds `announceOnMount` to satisfy linter (a11y) [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057) [[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238) https://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31 ### 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 37bc98a)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 30, 2025
…hange in Single Metric Viewer (elastic#236724) ## Summary Fixes elastic#224882 This PR: 1. Explicitly resets the value of showForecastCheckbox [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854) Also, it resets the value to default on `fullRestore` [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446) Previously `showForecastCheckbox` value was lingering after we switched the job. 2. Adds `announceOnMount` to satisfy linter (a11y) [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057) [[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238) https://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31 ### 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 37bc98a)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 30, 2025
…hange in Single Metric Viewer (elastic#236724) ## Summary Fixes elastic#224882 This PR: 1. Explicitly resets the value of showForecastCheckbox [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854) Also, it resets the value to default on `fullRestore` [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446) Previously `showForecastCheckbox` value was lingering after we switched the job. 2. Adds `announceOnMount` to satisfy linter (a11y) [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057) [[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238) https://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31 ### 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 37bc98a)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
VladimirFilonov
pushed a commit
to VladimirFilonov/kibana
that referenced
this pull request
Sep 30, 2025
…hange in Single Metric Viewer (elastic#236724) ## Summary Fixes elastic#224882 This PR: 1. Explicitly resets the value of showForecastCheckbox [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854) Also, it resets the value to default on `fullRestore` [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446) Previously `showForecastCheckbox` value was lingering after we switched the job. 2. Adds `announceOnMount` to satisfy linter (a11y) [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057) [[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238) https://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31 ### 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
kibanamachine
added a commit
that referenced
this pull request
Sep 30, 2025
…tion change in Single Metric Viewer (#236724) (#236925) # Backport This will backport the following commits from `main` to `9.0`: - [[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)](#236724) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Krasocki","email":"104936644+KodeRad@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-09-30T10:42:08Z","message":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)\n\n## Summary\n\nFixes #224882\n\nThis PR:\n\n1. Explicitly resets the value of showForecastCheckbox\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854)\nAlso, it resets the value to default on `fullRestore`\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446)\n\nPreviously `showForecastCheckbox` value was lingering after we switched\nthe job.\n\n2. Adds `announceOnMount` to satisfy linter (a11y)\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057)\n[[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238)\n\n\n\n\n\nhttps://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31\n\n\n\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- [ ] [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- [ ] 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- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"37bc98a6caf344d03aa640729c5ec00d45583885","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:Anomaly Detection","Team:ML","backport:all-open","v9.2.0"],"title":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer","number":236724,"url":"https://github.com/elastic/kibana/pull/236724","mergeCommit":{"message":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)\n\n## Summary\n\nFixes #224882\n\nThis PR:\n\n1. Explicitly resets the value of showForecastCheckbox\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854)\nAlso, it resets the value to default on `fullRestore`\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446)\n\nPreviously `showForecastCheckbox` value was lingering after we switched\nthe job.\n\n2. Adds `announceOnMount` to satisfy linter (a11y)\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057)\n[[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238)\n\n\n\n\n\nhttps://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31\n\n\n\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- [ ] [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- [ ] 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- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"37bc98a6caf344d03aa640729c5ec00d45583885"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/236724","number":236724,"mergeCommit":{"message":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)\n\n## Summary\n\nFixes #224882\n\nThis PR:\n\n1. Explicitly resets the value of showForecastCheckbox\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854)\nAlso, it resets the value to default on `fullRestore`\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446)\n\nPreviously `showForecastCheckbox` value was lingering after we switched\nthe job.\n\n2. Adds `announceOnMount` to satisfy linter (a11y)\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057)\n[[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238)\n\n\n\n\n\nhttps://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31\n\n\n\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- [ ] [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- [ ] 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- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"37bc98a6caf344d03aa640729c5ec00d45583885"}}]}] BACKPORT--> Co-authored-by: Konrad Krasocki <104936644+KodeRad@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Sep 30, 2025
…tion change in Single Metric Viewer (#236724) (#236926) # Backport This will backport the following commits from `main` to `9.1`: - [[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)](#236724) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Krasocki","email":"104936644+KodeRad@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-09-30T10:42:08Z","message":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)\n\n## Summary\n\nFixes #224882\n\nThis PR:\n\n1. Explicitly resets the value of showForecastCheckbox\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854)\nAlso, it resets the value to default on `fullRestore`\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446)\n\nPreviously `showForecastCheckbox` value was lingering after we switched\nthe job.\n\n2. Adds `announceOnMount` to satisfy linter (a11y)\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057)\n[[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238)\n\n\n\n\n\nhttps://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31\n\n\n\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- [ ] [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- [ ] 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- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"37bc98a6caf344d03aa640729c5ec00d45583885","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:Anomaly Detection","Team:ML","backport:all-open","v9.2.0"],"title":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer","number":236724,"url":"https://github.com/elastic/kibana/pull/236724","mergeCommit":{"message":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)\n\n## Summary\n\nFixes #224882\n\nThis PR:\n\n1. Explicitly resets the value of showForecastCheckbox\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854)\nAlso, it resets the value to default on `fullRestore`\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446)\n\nPreviously `showForecastCheckbox` value was lingering after we switched\nthe job.\n\n2. Adds `announceOnMount` to satisfy linter (a11y)\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057)\n[[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238)\n\n\n\n\n\nhttps://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31\n\n\n\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- [ ] [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- [ ] 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- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"37bc98a6caf344d03aa640729c5ec00d45583885"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/236724","number":236724,"mergeCommit":{"message":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)\n\n## Summary\n\nFixes #224882\n\nThis PR:\n\n1. Explicitly resets the value of showForecastCheckbox\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854)\nAlso, it resets the value to default on `fullRestore`\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446)\n\nPreviously `showForecastCheckbox` value was lingering after we switched\nthe job.\n\n2. Adds `announceOnMount` to satisfy linter (a11y)\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057)\n[[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238)\n\n\n\n\n\nhttps://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31\n\n\n\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- [ ] [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- [ ] 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- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"37bc98a6caf344d03aa640729c5ec00d45583885"}}]}] BACKPORT--> Co-authored-by: Konrad Krasocki <104936644+KodeRad@users.noreply.github.com>
kibanamachine
added
v9.1.5
backport missing
Contributor
|
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
kibanamachine
added a commit
that referenced
this pull request
Oct 2, 2025
…ction change in Single Metric Viewer (#236724) (#236924) # Backport This will backport the following commits from `main` to `8.19`: - [[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)](#236724) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Krasocki","email":"104936644+KodeRad@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-09-30T10:42:08Z","message":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)\n\n## Summary\n\nFixes #224882\n\nThis PR:\n\n1. Explicitly resets the value of showForecastCheckbox\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854)\nAlso, it resets the value to default on `fullRestore`\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446)\n\nPreviously `showForecastCheckbox` value was lingering after we switched\nthe job.\n\n2. Adds `announceOnMount` to satisfy linter (a11y)\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057)\n[[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238)\n\n\n\n\n\nhttps://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31\n\n\n\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- [ ] [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- [ ] 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- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"37bc98a6caf344d03aa640729c5ec00d45583885","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:Anomaly Detection","Team:ML","backport:all-open","v9.2.0"],"title":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer","number":236724,"url":"https://github.com/elastic/kibana/pull/236724","mergeCommit":{"message":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)\n\n## Summary\n\nFixes #224882\n\nThis PR:\n\n1. Explicitly resets the value of showForecastCheckbox\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854)\nAlso, it resets the value to default on `fullRestore`\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446)\n\nPreviously `showForecastCheckbox` value was lingering after we switched\nthe job.\n\n2. Adds `announceOnMount` to satisfy linter (a11y)\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057)\n[[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238)\n\n\n\n\n\nhttps://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31\n\n\n\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- [ ] [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- [ ] 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- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"37bc98a6caf344d03aa640729c5ec00d45583885"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/236724","number":236724,"mergeCommit":{"message":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)\n\n## Summary\n\nFixes #224882\n\nThis PR:\n\n1. Explicitly resets the value of showForecastCheckbox\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854)\nAlso, it resets the value to default on `fullRestore`\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446)\n\nPreviously `showForecastCheckbox` value was lingering after we switched\nthe job.\n\n2. Adds `announceOnMount` to satisfy linter (a11y)\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057)\n[[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238)\n\n\n\n\n\nhttps://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31\n\n\n\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- [ ] [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- [ ] 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- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"37bc98a6caf344d03aa640729c5ec00d45583885"}}]}] BACKPORT--> Co-authored-by: Konrad Krasocki <104936644+KodeRad@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Oct 2, 2025
…ction change in Single Metric Viewer (#236724) (#236923) # Backport This will backport the following commits from `main` to `8.18`: - [[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)](#236724) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Krasocki","email":"104936644+KodeRad@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-09-30T10:42:08Z","message":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)\n\n## Summary\n\nFixes #224882\n\nThis PR:\n\n1. Explicitly resets the value of showForecastCheckbox\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854)\nAlso, it resets the value to default on `fullRestore`\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446)\n\nPreviously `showForecastCheckbox` value was lingering after we switched\nthe job.\n\n2. Adds `announceOnMount` to satisfy linter (a11y)\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057)\n[[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238)\n\n\n\n\n\nhttps://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31\n\n\n\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- [ ] [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- [ ] 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- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"37bc98a6caf344d03aa640729c5ec00d45583885","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:Anomaly Detection","Team:ML","backport:all-open","v9.2.0"],"title":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer","number":236724,"url":"https://github.com/elastic/kibana/pull/236724","mergeCommit":{"message":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)\n\n## Summary\n\nFixes #224882\n\nThis PR:\n\n1. Explicitly resets the value of showForecastCheckbox\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854)\nAlso, it resets the value to default on `fullRestore`\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446)\n\nPreviously `showForecastCheckbox` value was lingering after we switched\nthe job.\n\n2. Adds `announceOnMount` to satisfy linter (a11y)\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057)\n[[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238)\n\n\n\n\n\nhttps://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31\n\n\n\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- [ ] [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- [ ] 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- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"37bc98a6caf344d03aa640729c5ec00d45583885"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/236724","number":236724,"mergeCommit":{"message":"[ML] [Anomaly Detection] Hide Show Forecast button on Job selection change in Single Metric Viewer (#236724)\n\n## Summary\n\nFixes #224882\n\nThis PR:\n\n1. Explicitly resets the value of showForecastCheckbox\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854)\nAlso, it resets the value to default on `fullRestore`\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446)\n\nPreviously `showForecastCheckbox` value was lingering after we switched\nthe job.\n\n2. Adds `announceOnMount` to satisfy linter (a11y)\n[[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057)\n[[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238)\n\n\n\n\n\nhttps://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31\n\n\n\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- [ ] [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- [ ] 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- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"37bc98a6caf344d03aa640729c5ec00d45583885"}}]}] BACKPORT--> Co-authored-by: Konrad Krasocki <104936644+KodeRad@users.noreply.github.com>
kibanamachine
added
v8.18.8
and removed
backport missing
rylnd
pushed a commit
to rylnd/kibana
that referenced
this pull request
Oct 17, 2025
…hange in Single Metric Viewer (elastic#236724) ## Summary Fixes elastic#224882 This PR: 1. Explicitly resets the value of showForecastCheckbox [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R852-R854) Also, it resets the value to default on `fullRestore` [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R446) Previously `showForecastCheckbox` value was lingering after we switched the job. 2. Adds `announceOnMount` to satisfy linter (a11y) [[1]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1057) [[2]](https://github.com/elastic/kibana/pull/236724/files#diff-350529a21f14f899831c0b5220e4b94c50b17090fb1e644d55d484189a0f0ad4R1238) https://github.com/user-attachments/assets/68030b1a-fe9c-4427-a814-615f54599c31 ### 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
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
5 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
Fixes #224882
This PR:
fullRestore[1]Previously
showForecastCheckboxvalue was lingering after we switched the job.announceOnMountto satisfy linter (a11y) [1] [2]forecast-fix2.mp4
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.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.