Update Risk severity color map to EUI Borealis #222061
Merged
albertoblaz merged 2 commits intoelastic:mainfrom Jun 4, 2025
Merged
Update Risk severity color map to EUI Borealis #222061albertoblaz merged 2 commits intoelastic:mainfrom
albertoblaz merged 2 commits intoelastic:mainfrom
Conversation
albertoblaz
added
release_note:enhancement
Team:Cloud Security
albertoblaz
force-pushed
the
asset-inv-risk-colors
branch
from
8a0b595 to
4adcad3
Compare
Contributor
|
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
Contributor
|
You need to update the branch to remove the Serverless and OAS changes the CI committed. |
albertoblaz
force-pushed
the
asset-inv-risk-colors
branch
from
baa08f0 to
6bb5f17
Compare
Contributor
|
Starting backport for target branches: 9.0 https://github.com/elastic/kibana/actions/runs/15447233908 |
Contributor
💚 Build Succeeded
Metrics [docs]Async chunks
Page load bundle
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
cc @albertoblaz |
Contributor
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
Contributor
Author
|
I've decided not to backport to v9.0 since these new color palette does not 100% map with existing color tokens in 9.0 |
albertoblaz
added
backport:skip
nickpeihl
pushed a commit
to nickpeihl/kibana
that referenced
this pull request
Jun 12, 2025
## Summary Solves this issue in relation to Risk severity in the context of Security solution: - elastic/security-team#11516 Map risk severity color map to the new color tokens in EUI Borealis ([see new pattern](https://eui.elastic.co/docs/patterns/severity/index.html)). These new color tokens were introduced through this PR: - elastic/eui#8601 ### Checklist - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [x] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks This is a low-risk change that only presents different colors where risk severity is used.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Solves this issue in relation to Risk severity in the context of Security solution:
Map risk severity color map to the new color tokens in EUI Borealis (see new pattern).
These new color tokens were introduced through this PR:
Checklist
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesIdentify risks
This is a low-risk change that only presents different colors where risk severity is used.