Skip to content

[Discover] Add 'Copy value' button to field value cells (#217457)#218817

Merged
AlexGPlay merged 13 commits intoelastic:mainfrom
AlexGPlay:217457-add-copy-value
May 5, 2025
Merged

[Discover] Add 'Copy value' button to field value cells (#217457)#218817
AlexGPlay merged 13 commits intoelastic:mainfrom
AlexGPlay:217457-add-copy-value

Conversation

@AlexGPlay
Copy link
Contributor

@AlexGPlay AlexGPlay commented Apr 22, 2025

Summary

Added a "Copy value" button to the field value cells.

chrome-capture-2025-4-23

Solves #217457

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests 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
  • 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 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

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.

@AlexGPlay AlexGPlay self-assigned this Apr 22, 2025
@AlexGPlay AlexGPlay force-pushed the 217457-add-copy-value branch from 3632859 to 6193ffe Compare April 22, 2025 13:06
@AlexGPlay AlexGPlay added Feature:UnifiedDocViewer Issues relating to the unified doc viewer component Team:DataDiscovery Discover, search (data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. t// labels Apr 22, 2025
@AlexGPlay AlexGPlay linked an issue Apr 22, 2025 that may be closed by this pull request
iconType="copyClipboard"
title={copyLabel}
flush="left"
onClick={() => copyToClipboard(String(flattenedValue))}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

i was wondering if this action should have some feedback, maybe something like a toast

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, that would be nice!

For example for the main Discover table it's handled in

export const copyValueToClipboard = ({
rowIndex,
columnId,
toastNotifications,
valueToStringConverter,
}: {
rowIndex: number;
columnId: string;
toastNotifications: ToastsStart;
valueToStringConverter: ValueToStringConverter;
}): string | null => {
const result = valueToStringConverter(rowIndex, columnId);
const valueFormatted = result.formattedString;
const copied = copyToClipboard(valueFormatted);
if (!copied) {
toastNotifications.addWarning({
title: COPY_FAILED_ERROR_MESSAGE,
});
return null;
}
const toastTitle = i18n.translate('unifiedDataTable.copyValueToClipboard.toastTitle', {
defaultMessage: 'Copied to clipboard',
});
if (result.withFormula) {
toastNotifications.addWarning({
title: toastTitle,
text: WARNING_FOR_FORMULAS,
});
} else {
toastNotifications.addInfo({
title: toastTitle,
});
}
return valueFormatted;
};

Also, it should be copying the text representation of the value (example:

). It's done because the value we render can include html tags (for links and images which users can configure via choosing a formatter for the data view field) and we don't want them to be copied. We want it to be copied as text only. In DocViewer I think it can be achieved if we take row.formattedAsText instead of row.flattenedValue.

@AlexGPlay AlexGPlay force-pushed the 217457-add-copy-value branch from 6eee8fb to 4263dca Compare April 23, 2025 08:24
Comment on lines +20 to +31
jest.mock('@elastic/eui', () => ({
...jest.requireActual('@elastic/eui'),
copyToClipboard: jest.fn(),
}));
const mockCopyToClipboard = jest.mocked(copyToClipboard);

const toastsMock = notificationServiceMock.createSetupContract().toasts;

afterEach(() => {
jest.clearAllMocks();
});
Copy link
Contributor Author

Choose a reason for hiding this comment

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

are we ok with mocking some code like copyToClipboard to check that it's getting called and test the code branches depending on its return?

@AlexGPlay AlexGPlay marked this pull request as ready for review April 23, 2025 15:04
@AlexGPlay AlexGPlay requested a review from a team as a code owner April 23, 2025 15:04
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

Copy link
Contributor

@jughosta jughosta left a comment

Choose a reason for hiding this comment

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

That's a very nice enhancement! Thanks for working on it, @AlexGPlay!

I left some comments but overall looks good!

Component: EuiDataGridColumnCellActionProps['Component'];
row: FieldRow | undefined; // as we pass `rows[rowIndex]` it's safer to assume that `row` prop can be undefined
isEsqlMode: boolean | undefined;
isEsqlMode?: boolean | undefined;
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are we changing this type? It would become easy to forget passing it to the component.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I changed it because the Copy one doesn't need it but happy to just pass it as undefined

return null;
}

const { formattedAsText, name } = row;
Copy link
Contributor

Choose a reason for hiding this comment

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

Since formattedAsText is a custom getter with caching logic, it would be better to access it from onClick handler instead of when Copy component is rendered to prevent unnecessary computations.

}
);

const Copy: React.FC<TableActionsProps & { toasts: IToasts }> = ({ Component, row, toasts }) => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
const Copy: React.FC<TableActionsProps & { toasts: IToasts }> = ({ Component, row, toasts }) => {
const Copy: React.FC<Omit<TableActionsProps, 'isEsqlMode'> & { toasts: IToasts }> = ({ Component, row, toasts }) => {

Let's drop isEsqlMode for this component in the its type instead.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

sounds good 🙌🏻

@AlexGPlay AlexGPlay force-pushed the 217457-add-copy-value branch 2 times, most recently from dc6511f to 7939438 Compare April 28, 2025 07:04
return;
}

const copied = copyToClipboard(row.formattedAsText);
Copy link
Contributor

@jughosta jughosta Apr 28, 2025

Choose a reason for hiding this comment

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

Hi @AlexGPlay,

I have been testing your work and realized that row.formattedAsText does not actually fit for this action. Sorry for misleading!

The problem with it that for most of the fields it returns an array representation as that's the nature of Elasticsearch Fields API. For example, when I see zip value for extension field in the table, the copied value for it is ["zip"]. I checked closely what we have for Copy action inside UnifiedDataTable and we format each item of the array separately and then concatenate.

Let's switch to calling

as it's implemented in UnifiedDataTable. I think we could extract this helper to discover-utils package and import it from UnifiedDataTable and UnifiedDocViewer. Also instead of passing rows and rowIndex it could be a rowFlattened value.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No problem! I'll do that, extract the convertValueToString to discover-utils and change both places to use it - thank you for the review 🙌🏻

@AlexGPlay AlexGPlay requested a review from a team as a code owner April 29, 2025 14:35
@AlexGPlay AlexGPlay force-pushed the 217457-add-copy-value branch from 9e6d9e9 to d8632b6 Compare April 30, 2025 11:39
Copy link
Contributor

@jughosta jughosta left a comment

Choose a reason for hiding this comment

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

This feature is super helpful, thanks for adding it! LGTM 👍

@AlexGPlay AlexGPlay force-pushed the 217457-add-copy-value branch from d8632b6 to 840d148 Compare May 5, 2025 07:13
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
apm 1872 1873 +1
canvas 1307 1308 +1
cloudSecurityPosture 671 672 +1
datasetQuality 431 432 +1
discover 1228 1229 +1
esqlDataGrid 410 411 +1
eventAnnotationListing 579 580 +1
lens 1346 1347 +1
logsShared 337 338 +1
observability 1279 1280 +1
searchPlayground 334 335 +1
securitySolution 7322 7323 +1
slo 1107 1108 +1
unifiedDocViewer 311 312 +1
total +14

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/discover-utils 288 296 +8

Async chunks

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

id before after diff
cloudSecurityPosture 517.2KB 517.4KB +306.0B
discover 1001.8KB 1002.1KB +321.0B
esqlDataGrid 155.4KB 155.7KB +297.0B
securitySolution 9.1MB 9.1MB +297.0B
slo 908.5KB 908.8KB +302.0B
unifiedDocViewer 207.7KB 209.3KB +1.6KB
total +3.1KB

Page load bundle

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

id before after diff
cloudSecurityPosture 18.0KB 18.0KB +1.0B
unifiedDocViewer 12.3KB 12.5KB +167.0B
total +168.0B
Unknown metric groups

API count

id before after diff
@kbn/discover-utils 338 346 +8

History

cc @AlexGPlay

Copy link
Contributor

@janmonschke janmonschke left a comment

Choose a reason for hiding this comment

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

THI changes lgtm

@AlexGPlay AlexGPlay merged commit d1a7c7b into elastic:main May 5, 2025
9 checks passed
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.19

https://github.com/elastic/kibana/actions/runs/14835563650

@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
8.19 Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 218817

Questions ?

Please refer to the Backport tool documentation

@AlexGPlay
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

AlexGPlay added a commit to AlexGPlay/kibana that referenced this pull request May 6, 2025
…) (elastic#218817)

## Summary

Added a "Copy value" button to the field value cells.

![chrome-capture-2025-4-23](https://github.com/user-attachments/assets/fb8d4815-9acd-47ab-b266-22008c9d22ac)

Solves elastic#217457

### 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

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

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit d1a7c7b)

# Conflicts:
#	src/platform/packages/shared/kbn-discover-utils/src/utils/index.ts
#	src/platform/packages/shared/kbn-discover-utils/tsconfig.json
AlexGPlay added a commit that referenced this pull request May 6, 2025
…) (#218817) (#220191)

# Backport

This will backport the following commits from `main` to `8.19`:
- [[Discover] Add 'Copy value' button to field value cells (#217457)
(#218817)](#218817)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Alejandro García
Parrondo","email":"31973472+AlexGPlay@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-05-05T11:38:43Z","message":"[Discover]
Add 'Copy value' button to field value cells (#217457) (#218817)\n\n##
Summary\n\nAdded a \"Copy value\" button to the field value
cells.\n\n\n![chrome-capture-2025-4-23](https://github.com/user-attachments/assets/fb8d4815-9acd-47ab-b266-22008c9d22ac)\n\nSolves
https://github.com/elastic/kibana/issues/217457\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\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-
[ ] ...\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d1a7c7bd52335f855f83d7e55453c86c960b5481","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:DataDiscovery","Feature:UnifiedDocViewer","backport:version","v9.1.0","v8.19.0"],"title":"[Discover]
Add 'Copy value' button to field value cells
(#217457)","number":218817,"url":"https://github.com/elastic/kibana/pull/218817","mergeCommit":{"message":"[Discover]
Add 'Copy value' button to field value cells (#217457) (#218817)\n\n##
Summary\n\nAdded a \"Copy value\" button to the field value
cells.\n\n\n![chrome-capture-2025-4-23](https://github.com/user-attachments/assets/fb8d4815-9acd-47ab-b266-22008c9d22ac)\n\nSolves
https://github.com/elastic/kibana/issues/217457\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\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-
[ ] ...\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d1a7c7bd52335f855f83d7e55453c86c960b5481"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218817","number":218817,"mergeCommit":{"message":"[Discover]
Add 'Copy value' button to field value cells (#217457) (#218817)\n\n##
Summary\n\nAdded a \"Copy value\" button to the field value
cells.\n\n\n![chrome-capture-2025-4-23](https://github.com/user-attachments/assets/fb8d4815-9acd-47ab-b266-22008c9d22ac)\n\nSolves
https://github.com/elastic/kibana/issues/217457\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\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-
[ ] ...\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d1a7c7bd52335f855f83d7e55453c86c960b5481"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
akowalska622 pushed a commit to akowalska622/kibana that referenced this pull request May 29, 2025
…) (elastic#218817)

## Summary

Added a "Copy value" button to the field value cells.


![chrome-capture-2025-4-23](https://github.com/user-attachments/assets/fb8d4815-9acd-47ab-b266-22008c9d22ac)

Solves elastic#217457


### 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

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

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
qn895 pushed a commit to qn895/kibana that referenced this pull request Jun 3, 2025
…) (elastic#218817)

## Summary

Added a "Copy value" button to the field value cells.


![chrome-capture-2025-4-23](https://github.com/user-attachments/assets/fb8d4815-9acd-47ab-b266-22008c9d22ac)

Solves elastic#217457


### 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

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

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:version Backport to applied version labels Feature:UnifiedDocViewer Issues relating to the unified doc viewer component release_note:enhancement Team:DataDiscovery Discover, search (data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. t// v8.19.0 v9.1.0

5 participants