Skip to content

[Lens][Table] Add color by terms with color mappings#189895

Merged
nickofthyme merged 50 commits intoelastic:mainfrom
nickofthyme:color-mapping-tables
Aug 28, 2024
Merged

[Lens][Table] Add color by terms with color mappings#189895
nickofthyme merged 50 commits intoelastic:mainfrom
nickofthyme:color-mapping-tables

Conversation

@nickofthyme
Copy link
Copy Markdown
Contributor

@nickofthyme nickofthyme commented Aug 5, 2024

Summary

Adds support for coloring table cells by terms with color mappings assignments. Supported for both Rows and Metric dimensions.

Zight.Recording.2024-08-05.at.07.46.55.AM.mp4

closes #179322

Checklist

@nickofthyme nickofthyme added Team:Visualizations Team label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t// Feature:Lens release_note:feature Makes this part of the condensed release notes vis:table labels Aug 5, 2024
Copy link
Copy Markdown
Contributor Author

@nickofthyme nickofthyme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@teresaalvarezsoler & @MichaelMarcialis - Mostly complete POC still tweaking and updating/adding tests.

See a-la-carte deployment here. You might get a 502 gateway error at first or need to bypass the security but it eventually worked for me.

@teresaalvarezsoler
Copy link
Copy Markdown
Contributor

Hey @nickofthyme, thanks for creating the deployment, it looks great! I couldn't find any issues. One question, the fact that we apply the old color mappings by default, is it because we don't offer the new color mappings for numbers? (I think that's fine, just clarifying the reasoning behind)

Copy link
Copy Markdown
Contributor

@teresaalvarezsoler teresaalvarezsoler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks good to me from the user perspective.

Copy link
Copy Markdown
Contributor

@dej611 dej611 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had a first review pass, not much on the code side, but I think the default palette in this case should be changed.

Copy link
Copy Markdown
Contributor

@Heenawter Heenawter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving to unblock - still interested to see what @elastic/kibana-design says about the positioning of this tooltip icon, but definitely not worth blocking all this work 🙇

Current Option 1 - keep style, vertically align Option 2 - match style of controls tooltip icon
image image image

cc @MichaelMarcialis

@@ -15,22 +15,26 @@ import { Container } from './components/container/container';
import { ColorMapping } from './config';
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I observed this small bug when switching between categorical/numerical color palettes.

  1. Create a datatable with a last value dimension and categorical color palette set.
  2. switch to a numerical operation, like 'sum'
  3. Click on the color palette - the palette input is not filled properly. I'll pass you the video in a PM (github limits won't allow me to do so)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, fixed this in 77cd409

nickofthyme and others added 2 commits August 26, 2024 13:24
Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

@MichaelMarcialis MichaelMarcialis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for making those changes, @nickofthyme. Everything looks great. I left two final nits below, but nothing worth holding you up over. Assuming you're able to address them, I'll approve now.

@kibana-ci
Copy link
Copy Markdown

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
lens 1505 1513 +8

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id before after diff
@kbn/chart-expressions-common 19 21 +2
@kbn/coloring 180 188 +8
lens 583 586 +3
total +13

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
dashboard 546.7KB 547.3KB +643.0B
expressionXY 129.3KB 129.3KB +62.0B
lens 1.5MB 1.5MB +7.1KB
total +7.8KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
expressionPartitionVis 29.0KB 29.1KB +168.0B
expressionTagcloud 13.1KB 13.2KB +168.0B
expressionXY 41.7KB 41.9KB +168.0B
fieldFormats 63.0KB 63.1KB +114.0B
lens 50.9KB 51.6KB +764.0B
total +1.3KB
Unknown metric groups

API count

id before after diff
@kbn/chart-expressions-common 23 25 +2
@kbn/coloring 217 227 +10
lens 685 688 +3
total +15

ESLint disabled line counts

id before after diff
lens 16 17 +1

Total ESLint disabled count

id before after diff
lens 16 17 +1

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@nickofthyme nickofthyme merged commit a994629 into elastic:main Aug 28, 2024
@kibanamachine kibanamachine added v8.16.0 backport:skip This PR does not require backporting labels Aug 28, 2024
wajihaparvez added a commit that referenced this pull request Nov 11, 2024
## Summary

Added a section with instructions for assigning colors to terms in a
table. The technical preview warning will be removed in GA.

Rel: #189895
Closes: [#559](elastic/platform-docs-team#559)

---------

Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Nov 11, 2024
## Summary

Added a section with instructions for assigning colors to terms in a
table. The technical preview warning will be removed in GA.

Rel: elastic#189895
Closes: [elastic#559](elastic/platform-docs-team#559)

---------

Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
(cherry picked from commit b781c4e)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Nov 11, 2024
## Summary

Added a section with instructions for assigning colors to terms in a
table. The technical preview warning will be removed in GA.

Rel: elastic#189895
Closes: [elastic#559](elastic/platform-docs-team#559)

---------

Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
(cherry picked from commit b781c4e)
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this pull request Nov 18, 2024
## Summary

Added a section with instructions for assigning colors to terms in a
table. The technical preview warning will be removed in GA.

Rel: elastic#189895
Closes: [elastic#559](elastic/platform-docs-team#559)

---------

Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
nickofthyme added a commit that referenced this pull request Feb 5, 2025
## Summary

In #189895 we added logic to the `getColorCategories` util function to
handle transpose columns. This mistakenly assumed the first row of the
datatable would include all transposed column ids (i.e.
`${value}---${columnId}`). After closer analysis this case is only
present the in datatable rendering (i.e. `table_basic.tsx`), but in this
context we also have the original non-transposed datatable.

So to simplify this we revert this logic to not care about transposed
datatables. Now the color mappings are correctly assigned across **split
by** columns.

<img width="720" alt="image"
src="https://github.com/user-attachments/assets/c588930e-53b9-409f-a257-2c5be35aaa38"
/>

Fixes #208555

### Checklist

- [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)

## Release note

Fixes an issue in Lens (#208555) Table where a split-by metric on a
terms rendered incorrect colors in table cells.

---------

Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
nickofthyme added a commit to nickofthyme/kibana that referenced this pull request Feb 5, 2025
…#208623)

## Summary

In elastic#189895 we added logic to the `getColorCategories` util function to
handle transpose columns. This mistakenly assumed the first row of the
datatable would include all transposed column ids (i.e.
`${value}---${columnId}`). After closer analysis this case is only
present the in datatable rendering (i.e. `table_basic.tsx`), but in this
context we also have the original non-transposed datatable.

So to simplify this we revert this logic to not care about transposed
datatables. Now the color mappings are correctly assigned across **split
by** columns.

<img width="720" alt="image"
src="https://github.com/user-attachments/assets/c588930e-53b9-409f-a257-2c5be35aaa38"
/>

Fixes elastic#208555

### Checklist

- [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)

## Release note

Fixes an issue in Lens (elastic#208555) Table where a split-by metric on a
terms rendered incorrect colors in table cells.

---------

Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
(cherry picked from commit a93aaee)
drewdaemon pushed a commit to drewdaemon/kibana that referenced this pull request Feb 6, 2025
…#208623)

## Summary

In elastic#189895 we added logic to the `getColorCategories` util function to
handle transpose columns. This mistakenly assumed the first row of the
datatable would include all transposed column ids (i.e.
`${value}---${columnId}`). After closer analysis this case is only
present the in datatable rendering (i.e. `table_basic.tsx`), but in this
context we also have the original non-transposed datatable.

So to simplify this we revert this logic to not care about transposed
datatables. Now the color mappings are correctly assigned across **split
by** columns.

<img width="720" alt="image"
src="https://github.com/user-attachments/assets/c588930e-53b9-409f-a257-2c5be35aaa38"
/>

Fixes elastic#208555

### Checklist

- [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)

## Release note

Fixes an issue in Lens (elastic#208555) Table where a split-by metric on a
terms rendered incorrect colors in table cells.

---------

Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
nickofthyme added a commit that referenced this pull request Feb 10, 2025
…208623) (#209927)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Lens][Datatable] Fix color mapping of transposed datatables
(#208623)](#208623)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Nick
Partridge","email":"nicholas.partridge@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T06:07:26Z","message":"[Lens][Datatable]
Fix color mapping of transposed datatables (#208623)\n\n##
Summary\r\n\r\nIn #189895 we added logic to the `getColorCategories`
util function to\r\nhandle transpose columns. This mistakenly assumed
the first row of the\r\ndatatable would include all transposed column
ids (i.e.\r\n`${value}---${columnId}`). After closer analysis this case
is only\r\npresent the in datatable rendering (i.e. `table_basic.tsx`),
but in this\r\ncontext we also have the original non-transposed
datatable.\r\n\r\nSo to simplify this we revert this logic to not care
about transposed\r\ndatatables. Now the color mappings are correctly
assigned across **split\r\nby** columns.\r\n\r\n<img width=\"720\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c588930e-53b9-409f-a257-2c5be35aaa38\"\r\n/>\r\n\r\nFixes
#208555\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] The PR
description includes the appropriate Release Notes section,\r\nand the
correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n##
Release note\r\n\r\nFixes an issue in Lens (#208555) Table where a
split-by metric on a\r\nterms rendered incorrect colors in table
cells.\r\n\r\n---------\r\n\r\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>\r\nCo-authored-by: Marco
Liberati
<dej611@users.noreply.github.com>","sha":"a93aaeee97d018c3e20c9cd1e26b8bc596986a58","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","backport:prev-major","v9.1.0"],"title":"[Lens][Datatable]
Fix color mapping of transposed
datatables","number":208623,"url":"https://github.com/elastic/kibana/pull/208623","mergeCommit":{"message":"[Lens][Datatable]
Fix color mapping of transposed datatables (#208623)\n\n##
Summary\r\n\r\nIn #189895 we added logic to the `getColorCategories`
util function to\r\nhandle transpose columns. This mistakenly assumed
the first row of the\r\ndatatable would include all transposed column
ids (i.e.\r\n`${value}---${columnId}`). After closer analysis this case
is only\r\npresent the in datatable rendering (i.e. `table_basic.tsx`),
but in this\r\ncontext we also have the original non-transposed
datatable.\r\n\r\nSo to simplify this we revert this logic to not care
about transposed\r\ndatatables. Now the color mappings are correctly
assigned across **split\r\nby** columns.\r\n\r\n<img width=\"720\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c588930e-53b9-409f-a257-2c5be35aaa38\"\r\n/>\r\n\r\nFixes
#208555\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] The PR
description includes the appropriate Release Notes section,\r\nand the
correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n##
Release note\r\n\r\nFixes an issue in Lens (#208555) Table where a
split-by metric on a\r\nterms rendered incorrect colors in table
cells.\r\n\r\n---------\r\n\r\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>\r\nCo-authored-by: Marco
Liberati
<dej611@users.noreply.github.com>","sha":"a93aaeee97d018c3e20c9cd1e26b8bc596986a58"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208623","number":208623,"mergeCommit":{"message":"[Lens][Datatable]
Fix color mapping of transposed datatables (#208623)\n\n##
Summary\r\n\r\nIn #189895 we added logic to the `getColorCategories`
util function to\r\nhandle transpose columns. This mistakenly assumed
the first row of the\r\ndatatable would include all transposed column
ids (i.e.\r\n`${value}---${columnId}`). After closer analysis this case
is only\r\npresent the in datatable rendering (i.e. `table_basic.tsx`),
but in this\r\ncontext we also have the original non-transposed
datatable.\r\n\r\nSo to simplify this we revert this logic to not care
about transposed\r\ndatatables. Now the color mappings are correctly
assigned across **split\r\nby** columns.\r\n\r\n<img width=\"720\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c588930e-53b9-409f-a257-2c5be35aaa38\"\r\n/>\r\n\r\nFixes
#208555\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] The PR
description includes the appropriate Release Notes section,\r\nand the
correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n##
Release note\r\n\r\nFixes an issue in Lens (#208555) Table where a
split-by metric on a\r\nterms rendered incorrect colors in table
cells.\r\n\r\n---------\r\n\r\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>\r\nCo-authored-by: Marco
Liberati
<dej611@users.noreply.github.com>","sha":"a93aaeee97d018c3e20c9cd1e26b8bc596986a58"}}]}]
BACKPORT-->

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
nickofthyme added a commit that referenced this pull request Feb 10, 2025
…208623) (#209924)

# Backport

This will backport the following commits from `main` to `9.0`:
- [[Lens][Datatable] Fix color mapping of transposed datatables
(#208623)](#208623)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Nick
Partridge","email":"nicholas.partridge@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T06:07:26Z","message":"[Lens][Datatable]
Fix color mapping of transposed datatables (#208623)\n\n##
Summary\r\n\r\nIn #189895 we added logic to the `getColorCategories`
util function to\r\nhandle transpose columns. This mistakenly assumed
the first row of the\r\ndatatable would include all transposed column
ids (i.e.\r\n`${value}---${columnId}`). After closer analysis this case
is only\r\npresent the in datatable rendering (i.e. `table_basic.tsx`),
but in this\r\ncontext we also have the original non-transposed
datatable.\r\n\r\nSo to simplify this we revert this logic to not care
about transposed\r\ndatatables. Now the color mappings are correctly
assigned across **split\r\nby** columns.\r\n\r\n<img width=\"720\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c588930e-53b9-409f-a257-2c5be35aaa38\"\r\n/>\r\n\r\nFixes
#208555\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] The PR
description includes the appropriate Release Notes section,\r\nand the
correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n##
Release note\r\n\r\nFixes an issue in Lens (#208555) Table where a
split-by metric on a\r\nterms rendered incorrect colors in table
cells.\r\n\r\n---------\r\n\r\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>\r\nCo-authored-by: Marco
Liberati
<dej611@users.noreply.github.com>","sha":"a93aaeee97d018c3e20c9cd1e26b8bc596986a58","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","backport:prev-major","v9.1.0"],"title":"[Lens][Datatable]
Fix color mapping of transposed
datatables","number":208623,"url":"https://github.com/elastic/kibana/pull/208623","mergeCommit":{"message":"[Lens][Datatable]
Fix color mapping of transposed datatables (#208623)\n\n##
Summary\r\n\r\nIn #189895 we added logic to the `getColorCategories`
util function to\r\nhandle transpose columns. This mistakenly assumed
the first row of the\r\ndatatable would include all transposed column
ids (i.e.\r\n`${value}---${columnId}`). After closer analysis this case
is only\r\npresent the in datatable rendering (i.e. `table_basic.tsx`),
but in this\r\ncontext we also have the original non-transposed
datatable.\r\n\r\nSo to simplify this we revert this logic to not care
about transposed\r\ndatatables. Now the color mappings are correctly
assigned across **split\r\nby** columns.\r\n\r\n<img width=\"720\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c588930e-53b9-409f-a257-2c5be35aaa38\"\r\n/>\r\n\r\nFixes
#208555\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] The PR
description includes the appropriate Release Notes section,\r\nand the
correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n##
Release note\r\n\r\nFixes an issue in Lens (#208555) Table where a
split-by metric on a\r\nterms rendered incorrect colors in table
cells.\r\n\r\n---------\r\n\r\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>\r\nCo-authored-by: Marco
Liberati
<dej611@users.noreply.github.com>","sha":"a93aaeee97d018c3e20c9cd1e26b8bc596986a58"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208623","number":208623,"mergeCommit":{"message":"[Lens][Datatable]
Fix color mapping of transposed datatables (#208623)\n\n##
Summary\r\n\r\nIn #189895 we added logic to the `getColorCategories`
util function to\r\nhandle transpose columns. This mistakenly assumed
the first row of the\r\ndatatable would include all transposed column
ids (i.e.\r\n`${value}---${columnId}`). After closer analysis this case
is only\r\npresent the in datatable rendering (i.e. `table_basic.tsx`),
but in this\r\ncontext we also have the original non-transposed
datatable.\r\n\r\nSo to simplify this we revert this logic to not care
about transposed\r\ndatatables. Now the color mappings are correctly
assigned across **split\r\nby** columns.\r\n\r\n<img width=\"720\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c588930e-53b9-409f-a257-2c5be35aaa38\"\r\n/>\r\n\r\nFixes
#208555\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] The PR
description includes the appropriate Release Notes section,\r\nand the
correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n##
Release note\r\n\r\nFixes an issue in Lens (#208555) Table where a
split-by metric on a\r\nterms rendered incorrect colors in table
cells.\r\n\r\n---------\r\n\r\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>\r\nCo-authored-by: Marco
Liberati
<dej611@users.noreply.github.com>","sha":"a93aaeee97d018c3e20c9cd1e26b8bc596986a58"}}]}]
BACKPORT-->

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
@nickofthyme nickofthyme deleted the color-mapping-tables branch July 30, 2025 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting Feature:Lens release_note:feature Makes this part of the condensed release notes Team:Visualizations Team label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t// v8.16.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Lens] Color options for string cells in tables