[Fleet] Remove stream toggle when an input only has a single stream #219287
Merged
Supplementing merged 9 commits intoelastic:mainfrom Apr 29, 2025
Merged
Conversation
Supplementing
added
release_note:skip
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
Author
|
@elasticmachine merge upstream |
…hub.com/Supplementing/kibana into enhancement-remove-single-stream-toggle
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
|
akowalska622
pushed a commit
to akowalska622/kibana
that referenced
this pull request
Apr 30, 2025
…lastic#219287) ## Summary Closes elastic#192588 - Removed toggle when an input only has one stream as the top-level toggle controls it anyway. The toggles will only be nested when there is more than one stream per input. Before: <img width="1512" alt="Screenshot 2025-04-25 at 10 53 51 AM" src="https://github.com/user-attachments/assets/2edb8108-e1e8-41f0-ae9f-666aa815b10e" /> After: <img width="1505" alt="image" src="https://github.com/user-attachments/assets/a90df067-8d13-42e9-be16-2a0723dfd227" /> ### 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) ### Identify risks N/A --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
akowalska622
pushed a commit
to akowalska622/kibana
that referenced
this pull request
May 29, 2025
…lastic#219287) ## Summary Closes elastic#192588 - Removed toggle when an input only has one stream as the top-level toggle controls it anyway. The toggles will only be nested when there is more than one stream per input. Before: <img width="1512" alt="Screenshot 2025-04-25 at 10 53 51 AM" src="https://github.com/user-attachments/assets/2edb8108-e1e8-41f0-ae9f-666aa815b10e" /> After: <img width="1505" alt="image" src="https://github.com/user-attachments/assets/a90df067-8d13-42e9-be16-2a0723dfd227" /> ### 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) ### Identify risks N/A --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
juliaElastic
added a commit
that referenced
this pull request
Feb 16, 2026
## Summary Fix bug introduced in #219287 and reported with FIM integration, if the data stream has no vars, the description was rendered as `undefined`. Before: <img width="1486" height="238" alt="image" src="https://github.com/user-attachments/assets/3a296fa8-3ca8-4de4-bfc6-5529680f0aa0" /> After: <img width="928" height="864" alt="image" src="https://github.com/user-attachments/assets/8dba9583-17f5-4170-8771-a808b26f62a9" /> ### 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
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 16, 2026
…ic#253226) ## Summary Fix bug introduced in elastic#219287 and reported with FIM integration, if the data stream has no vars, the description was rendered as `undefined`. Before: <img width="1486" height="238" alt="image" src="https://github.com/user-attachments/assets/3a296fa8-3ca8-4de4-bfc6-5529680f0aa0" /> After: <img width="928" height="864" alt="image" src="https://github.com/user-attachments/assets/8dba9583-17f5-4170-8771-a808b26f62a9" /> ### 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 b67be74)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 16, 2026
…ic#253226) ## Summary Fix bug introduced in elastic#219287 and reported with FIM integration, if the data stream has no vars, the description was rendered as `undefined`. Before: <img width="1486" height="238" alt="image" src="https://github.com/user-attachments/assets/3a296fa8-3ca8-4de4-bfc6-5529680f0aa0" /> After: <img width="928" height="864" alt="image" src="https://github.com/user-attachments/assets/8dba9583-17f5-4170-8771-a808b26f62a9" /> ### 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 b67be74)
kibanamachine
added a commit
that referenced
this pull request
Feb 16, 2026
…253226) (#253254) # Backport This will backport the following commits from `main` to `9.3`: - [[Fleet] hide description if there are no visible input streams (#253226)](#253226) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-02-16T13:32:19Z","message":"[Fleet] hide description if there are no visible input streams (#253226)\n\n## Summary\n\nFix bug introduced in #219287 and\nreported with FIM integration, if the data stream has no vars, the\ndescription was rendered as `undefined`.\n\nBefore:\n<img width=\"1486\" height=\"238\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3a296fa8-3ca8-4de4-bfc6-5529680f0aa0\"\n/>\n\nAfter:\n<img width=\"928\" height=\"864\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/8dba9583-17f5-4170-8771-a808b26f62a9\"\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":"b67be74e7b07beff2f8dbba1316b76929f929949","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:version","v9.4.0","v9.3.1","v9.2.6"],"title":"[Fleet] hide description if there are no visible input streams","number":253226,"url":"https://github.com/elastic/kibana/pull/253226","mergeCommit":{"message":"[Fleet] hide description if there are no visible input streams (#253226)\n\n## Summary\n\nFix bug introduced in #219287 and\nreported with FIM integration, if the data stream has no vars, the\ndescription was rendered as `undefined`.\n\nBefore:\n<img width=\"1486\" height=\"238\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3a296fa8-3ca8-4de4-bfc6-5529680f0aa0\"\n/>\n\nAfter:\n<img width=\"928\" height=\"864\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/8dba9583-17f5-4170-8771-a808b26f62a9\"\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":"b67be74e7b07beff2f8dbba1316b76929f929949"}},"sourceBranch":"main","suggestedTargetBranches":["9.3","9.2"],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/253226","number":253226,"mergeCommit":{"message":"[Fleet] hide description if there are no visible input streams (#253226)\n\n## Summary\n\nFix bug introduced in #219287 and\nreported with FIM integration, if the data stream has no vars, the\ndescription was rendered as `undefined`.\n\nBefore:\n<img width=\"1486\" height=\"238\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3a296fa8-3ca8-4de4-bfc6-5529680f0aa0\"\n/>\n\nAfter:\n<img width=\"928\" height=\"864\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/8dba9583-17f5-4170-8771-a808b26f62a9\"\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":"b67be74e7b07beff2f8dbba1316b76929f929949"}},{"branch":"9.3","label":"v9.3.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Feb 17, 2026
…253226) (#253253) # Backport This will backport the following commits from `main` to `9.2`: - [[Fleet] hide description if there are no visible input streams (#253226)](#253226) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-02-16T13:32:19Z","message":"[Fleet] hide description if there are no visible input streams (#253226)\n\n## Summary\n\nFix bug introduced in #219287 and\nreported with FIM integration, if the data stream has no vars, the\ndescription was rendered as `undefined`.\n\nBefore:\n<img width=\"1486\" height=\"238\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3a296fa8-3ca8-4de4-bfc6-5529680f0aa0\"\n/>\n\nAfter:\n<img width=\"928\" height=\"864\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/8dba9583-17f5-4170-8771-a808b26f62a9\"\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":"b67be74e7b07beff2f8dbba1316b76929f929949","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:version","v9.4.0","v9.3.1","v9.2.6"],"title":"[Fleet] hide description if there are no visible input streams","number":253226,"url":"https://github.com/elastic/kibana/pull/253226","mergeCommit":{"message":"[Fleet] hide description if there are no visible input streams (#253226)\n\n## Summary\n\nFix bug introduced in #219287 and\nreported with FIM integration, if the data stream has no vars, the\ndescription was rendered as `undefined`.\n\nBefore:\n<img width=\"1486\" height=\"238\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3a296fa8-3ca8-4de4-bfc6-5529680f0aa0\"\n/>\n\nAfter:\n<img width=\"928\" height=\"864\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/8dba9583-17f5-4170-8771-a808b26f62a9\"\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":"b67be74e7b07beff2f8dbba1316b76929f929949"}},"sourceBranch":"main","suggestedTargetBranches":["9.3","9.2"],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/253226","number":253226,"mergeCommit":{"message":"[Fleet] hide description if there are no visible input streams (#253226)\n\n## Summary\n\nFix bug introduced in #219287 and\nreported with FIM integration, if the data stream has no vars, the\ndescription was rendered as `undefined`.\n\nBefore:\n<img width=\"1486\" height=\"238\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3a296fa8-3ca8-4de4-bfc6-5529680f0aa0\"\n/>\n\nAfter:\n<img width=\"928\" height=\"864\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/8dba9583-17f5-4170-8771-a808b26f62a9\"\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":"b67be74e7b07beff2f8dbba1316b76929f929949"}},{"branch":"9.3","label":"v9.3.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
paulinashakirova
pushed a commit
to paulinashakirova/kibana
that referenced
this pull request
Feb 17, 2026
…ic#253226) ## Summary Fix bug introduced in elastic#219287 and reported with FIM integration, if the data stream has no vars, the description was rendered as `undefined`. Before: <img width="1486" height="238" alt="image" src="https://github.com/user-attachments/assets/3a296fa8-3ca8-4de4-bfc6-5529680f0aa0" /> After: <img width="928" height="864" alt="image" src="https://github.com/user-attachments/assets/8dba9583-17f5-4170-8771-a808b26f62a9" /> ### 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) - [ ] ...
patrykkopycinski
pushed a commit
to patrykkopycinski/kibana
that referenced
this pull request
Feb 19, 2026
…ic#253226) ## Summary Fix bug introduced in elastic#219287 and reported with FIM integration, if the data stream has no vars, the description was rendered as `undefined`. Before: <img width="1486" height="238" alt="image" src="https://github.com/user-attachments/assets/3a296fa8-3ca8-4de4-bfc6-5529680f0aa0" /> After: <img width="928" height="864" alt="image" src="https://github.com/user-attachments/assets/8dba9583-17f5-4170-8771-a808b26f62a9" /> ### 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) - [ ] ...
ersin-erdal
pushed a commit
to ersin-erdal/kibana
that referenced
this pull request
Feb 19, 2026
…ic#253226) ## Summary Fix bug introduced in elastic#219287 and reported with FIM integration, if the data stream has no vars, the description was rendered as `undefined`. Before: <img width="1486" height="238" alt="image" src="https://github.com/user-attachments/assets/3a296fa8-3ca8-4de4-bfc6-5529680f0aa0" /> After: <img width="928" height="864" alt="image" src="https://github.com/user-attachments/assets/8dba9583-17f5-4170-8771-a808b26f62a9" /> ### 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) - [ ] ...
3 tasks
jen-huang
added a commit
that referenced
this pull request
Apr 23, 2026
…y editor (#264866) ## Summary Resolves #256854 This PR fixes the release badge (`Beta` label) not showing at the input title level for OTel packages (config needed to be expanded in order to see the label). While fixing that, I went down a bit of rabbit hole and found that the release badges and whitespace were just [odd](#256854 (comment)) for input-only packages and single-stream inputs. _(Jen going down a UI rabbit hole? Groundbreaking...)_ I believe this was due to #219287, #254721, and maybe other PRs as part of elastic/ingest-dev#6979. So this PR ended up tweaking conditions for various spacers and flex groups, so that they render (or don't render) correctly. **I recommend reviewing this PR with whitespace turned off.** <img width="794" height="476" alt="image" src="https://github.com/user-attachments/assets/c5253f08-785c-4524-8590-776b0577b110" /> . <img width="800" height="569" alt="image" src="https://github.com/user-attachments/assets/c6cd619f-9179-4a22-89eb-60699b91a293" /> ## Testing Test the policy editor - both in standalone page and in add integration flyout (from agent policy) - with various packages that have GA and non-GA data streams, input-only integrations and regular ones, etc. I tested ones like these: - Azure Event Hub Input - Istio - Nginx OTel - Apache - etc... ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
smith
pushed a commit
to smith/kibana
that referenced
this pull request
Apr 23, 2026
…y editor (elastic#264866) ## Summary Resolves elastic#256854 This PR fixes the release badge (`Beta` label) not showing at the input title level for OTel packages (config needed to be expanded in order to see the label). While fixing that, I went down a bit of rabbit hole and found that the release badges and whitespace were just [odd](elastic#256854 (comment)) for input-only packages and single-stream inputs. _(Jen going down a UI rabbit hole? Groundbreaking...)_ I believe this was due to elastic#219287, elastic#254721, and maybe other PRs as part of elastic/ingest-dev#6979. So this PR ended up tweaking conditions for various spacers and flex groups, so that they render (or don't render) correctly. **I recommend reviewing this PR with whitespace turned off.** <img width="794" height="476" alt="image" src="https://github.com/user-attachments/assets/c5253f08-785c-4524-8590-776b0577b110" /> . <img width="800" height="569" alt="image" src="https://github.com/user-attachments/assets/c6cd619f-9179-4a22-89eb-60699b91a293" /> ## Testing Test the policy editor - both in standalone page and in add integration flyout (from agent policy) - with various packages that have GA and non-GA data streams, input-only integrations and regular ones, etc. I tested ones like these: - Azure Event Hub Input - Istio - Nginx OTel - Apache - etc... ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
jen-huang
added a commit
that referenced
this pull request
Apr 23, 2026
… policy editor (#264866) (#265394) # Backport This will backport the following commits from `main` to `9.4`: - [[UII] Fix floating release badges and whitespace in integration policy editor (#264866)](#264866) <!--- Backport version: 11.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jen Huang","email":"its.jenetic@gmail.com"},"sourceCommit":{"committedDate":"2026-04-23T03:43:04Z","message":"[UII] Fix floating release badges and whitespace in integration policy editor (#264866)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/256854\n\nThis PR fixes the release badge (`Beta` label) not showing at the input\ntitle level for OTel packages (config needed to be expanded in order to\nsee the label).\n\nWhile fixing that, I went down a bit of rabbit hole and found that the\nrelease badges and whitespace were just\n[odd](https://github.com/elastic/kibana/issues/256854#issuecomment-4284722964)\nfor input-only packages and single-stream inputs. _(Jen going down a UI\nrabbit hole? Groundbreaking...)_ I believe this was due to\nhttps://github.com//pull/219287,\nhttps://github.com//pull/254721, and maybe other PRs as\npart of https://github.com/elastic/ingest-dev/issues/6979.\n\nSo this PR ended up tweaking conditions for various spacers and flex\ngroups, so that they render (or don't render) correctly. **I recommend\nreviewing this PR with whitespace turned off.**\n\n<img width=\"794\" height=\"476\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c5253f08-785c-4524-8590-776b0577b110\"\n/>\n.\n<img width=\"800\" height=\"569\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c6cd619f-9179-4a22-89eb-60699b91a293\"\n/>\n\n## Testing\nTest the policy editor - both in standalone page and in add integration\nflyout (from agent policy) - with various packages that have GA and\nnon-GA data streams, input-only integrations and regular ones, etc. I\ntested ones like these:\n- Azure Event Hub Input\n- Istio\n- Nginx OTel\n- Apache\n- etc...\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"8377aeaf3d7bfef40d814d85efa126b7a5e3cd10","branchLabelMapping":{"^v9.5.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:version","v9.4.0","v9.5.0"],"title":"[UII] Fix floating release badges and whitespace in integration policy editor","number":264866,"url":"https://github.com/elastic/kibana/pull/264866","mergeCommit":{"message":"[UII] Fix floating release badges and whitespace in integration policy editor (#264866)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/256854\n\nThis PR fixes the release badge (`Beta` label) not showing at the input\ntitle level for OTel packages (config needed to be expanded in order to\nsee the label).\n\nWhile fixing that, I went down a bit of rabbit hole and found that the\nrelease badges and whitespace were just\n[odd](https://github.com/elastic/kibana/issues/256854#issuecomment-4284722964)\nfor input-only packages and single-stream inputs. _(Jen going down a UI\nrabbit hole? Groundbreaking...)_ I believe this was due to\nhttps://github.com//pull/219287,\nhttps://github.com//pull/254721, and maybe other PRs as\npart of https://github.com/elastic/ingest-dev/issues/6979.\n\nSo this PR ended up tweaking conditions for various spacers and flex\ngroups, so that they render (or don't render) correctly. **I recommend\nreviewing this PR with whitespace turned off.**\n\n<img width=\"794\" height=\"476\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c5253f08-785c-4524-8590-776b0577b110\"\n/>\n.\n<img width=\"800\" height=\"569\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c6cd619f-9179-4a22-89eb-60699b91a293\"\n/>\n\n## Testing\nTest the policy editor - both in standalone page and in add integration\nflyout (from agent policy) - with various packages that have GA and\nnon-GA data streams, input-only integrations and regular ones, etc. I\ntested ones like these:\n- Azure Event Hub Input\n- Istio\n- Nginx OTel\n- Apache\n- etc...\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"8377aeaf3d7bfef40d814d85efa126b7a5e3cd10"}},"sourceBranch":"main","suggestedTargetBranches":["9.4"],"targetPullRequestStates":[{"branch":"9.4","label":"v9.4.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.5.0","branchLabelMappingKey":"^v9.5.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/264866","number":264866,"mergeCommit":{"message":"[UII] Fix floating release badges and whitespace in integration policy editor (#264866)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/256854\n\nThis PR fixes the release badge (`Beta` label) not showing at the input\ntitle level for OTel packages (config needed to be expanded in order to\nsee the label).\n\nWhile fixing that, I went down a bit of rabbit hole and found that the\nrelease badges and whitespace were just\n[odd](https://github.com/elastic/kibana/issues/256854#issuecomment-4284722964)\nfor input-only packages and single-stream inputs. _(Jen going down a UI\nrabbit hole? Groundbreaking...)_ I believe this was due to\nhttps://github.com//pull/219287,\nhttps://github.com//pull/254721, and maybe other PRs as\npart of https://github.com/elastic/ingest-dev/issues/6979.\n\nSo this PR ended up tweaking conditions for various spacers and flex\ngroups, so that they render (or don't render) correctly. **I recommend\nreviewing this PR with whitespace turned off.**\n\n<img width=\"794\" height=\"476\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c5253f08-785c-4524-8590-776b0577b110\"\n/>\n.\n<img width=\"800\" height=\"569\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c6cd619f-9179-4a22-89eb-60699b91a293\"\n/>\n\n## Testing\nTest the policy editor - both in standalone page and in add integration\nflyout (from agent policy) - with various packages that have GA and\nnon-GA data streams, input-only integrations and regular ones, etc. I\ntested ones like these:\n- Azure Event Hub Input\n- Istio\n- Nginx OTel\n- Apache\n- etc...\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"8377aeaf3d7bfef40d814d85efa126b7a5e3cd10"}}]}] BACKPORT-->
rbrtj
pushed a commit
to walterra/kibana
that referenced
this pull request
Apr 27, 2026
…y editor (elastic#264866) ## Summary Resolves elastic#256854 This PR fixes the release badge (`Beta` label) not showing at the input title level for OTel packages (config needed to be expanded in order to see the label). While fixing that, I went down a bit of rabbit hole and found that the release badges and whitespace were just [odd](elastic#256854 (comment)) for input-only packages and single-stream inputs. _(Jen going down a UI rabbit hole? Groundbreaking...)_ I believe this was due to elastic#219287, elastic#254721, and maybe other PRs as part of elastic/ingest-dev#6979. So this PR ended up tweaking conditions for various spacers and flex groups, so that they render (or don't render) correctly. **I recommend reviewing this PR with whitespace turned off.** <img width="794" height="476" alt="image" src="https://github.com/user-attachments/assets/c5253f08-785c-4524-8590-776b0577b110" /> . <img width="800" height="569" alt="image" src="https://github.com/user-attachments/assets/c6cd619f-9179-4a22-89eb-60699b91a293" /> ## Testing Test the policy editor - both in standalone page and in add integration flyout (from agent policy) - with various packages that have GA and non-GA data streams, input-only integrations and regular ones, etc. I tested ones like these: - Azure Event Hub Input - Istio - Nginx OTel - Apache - etc... ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
SoniaSanzV
pushed a commit
to SoniaSanzV/kibana
that referenced
this pull request
Apr 27, 2026
…y editor (elastic#264866) ## Summary Resolves elastic#256854 This PR fixes the release badge (`Beta` label) not showing at the input title level for OTel packages (config needed to be expanded in order to see the label). While fixing that, I went down a bit of rabbit hole and found that the release badges and whitespace were just [odd](elastic#256854 (comment)) for input-only packages and single-stream inputs. _(Jen going down a UI rabbit hole? Groundbreaking...)_ I believe this was due to elastic#219287, elastic#254721, and maybe other PRs as part of elastic/ingest-dev#6979. So this PR ended up tweaking conditions for various spacers and flex groups, so that they render (or don't render) correctly. **I recommend reviewing this PR with whitespace turned off.** <img width="794" height="476" alt="image" src="https://github.com/user-attachments/assets/c5253f08-785c-4524-8590-776b0577b110" /> . <img width="800" height="569" alt="image" src="https://github.com/user-attachments/assets/c6cd619f-9179-4a22-89eb-60699b91a293" /> ## Testing Test the policy editor - both in standalone page and in add integration flyout (from agent policy) - with various packages that have GA and non-GA data streams, input-only integrations and regular ones, etc. I tested ones like these: - Azure Event Hub Input - Istio - Nginx OTel - Apache - etc... ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #192588
Before:
After:
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 guidelinesIdentify risks
N/A