Separate export menu from share

[eokoneyo]

Summary

This PR extracts the share export functionality into a standalone triggered UI action, and builds mostly off of the work that's been done in #211665 as such any share integration type that's registered under the groupId export will show up within the afore mentioned standalone export type.

Registering a new export type would happen like so;

share.registerShareIntegration({
	groupId: 'export',
	...
	config: () => ({
		...
	}),
	prerequisiteCheck({ license, capabilities, objectType }) {
		// The prerequisiteCheck callback will get passed the license, app capabilities and the objectType
		// of the current caller, this can then be used to determine if this integration should be available,
		// returning false in here disables the integration, 
	}
})

P.S. This registration can also be scoped to a particular object type (i.e. lens, dashboard etc.) if said integration is intended to only be available for only a particular object type.

Visuals for new export experience

visualize

(lens)

(others)

dashboard

(user with all reporting permissions)

(user with no pdf, png, csv privileges doesn't have the export button visible)

discover

Test scenarios

• Pull this PR and run it locally, or test in the provision environment linked to this PR.
• Navigate to the dashboard, discover, and visualize app. The nav menu should display icon buttons for sharing and export.
• Clicking the "Share" icon (up arrow) opens the familiar share modal without export. The "Export" icon (down arrow) opens a new popover with available options.
• Export Functionality Test;
  • Single Export Option: When there's only one export option, the flyout opens automatically.
  • Disabled Reporting Features: Create a new role with reporting subPrivileges and test it by creating a user assigned to that role. Log in as the user, and the export popover should reflect the limited reporting features.
  • In the case where the current user has no registered integrations available to them, the export functionality will not be displayed

[eokoneyo]

/ci

[eokoneyo]

/ci

[eokoneyo]

/ci

[eokoneyo]

@elasticmachine merge upstream

[markov00]

I'm only approving the code changes around the our owned code.

Warning

I can't approve this PR from the design point of view. As specified in my comments, the current design doesn't offer a graceful interface for cases where we don't have much more to display then a very simple button. It feels incomplete, unnecessary "empty" (for the flyout) and at a first sight looks like something is broken, It doesn't seems better then the previous UX. Since we don't own the share menu components there is nothing we can do to block this. I hope we can find some better solution in a followup

[markov00]

Within Lens, clicking on the share button looks very empty and incomplete.
The Link tab is now there alone, with no content in it (as it was before, but at least before the share menu was containing also the export part to have a bit more "content".

I think we can probably find a better solution for this case.

[eokoneyo]

Hi @markov00 thanks for pointing this out... I'd look into this

[eokoneyo]

An issue(#222093) has been created whence which this will be resolved.

[markov00]

This flyout seems again very empty and incomplete. If there is no content to display, no information/choices/options to show, why are we showing the flyout?
I don't think in this case the UX consistency has more value than a good experience.

[ghudgins]

if it's okay with everyone, i'll work with @ek-so and @alexmarhaba on a quick follow-up PR to address these issues

[markov00]

Not sure why, but the export icon, when there is no data to export, has 2 different tooltip that actives one after the other. Was that a wanted behaviour?

Screen.Recording.2025-05-29.at.14.58.34.mp4

[ek-so]

Maybe we could simplify the text to "No data to export" / "No data to share"?

[eokoneyo]

If I understood @markov00's point correctly it's the fact that two tooltips are displayed when there's no data to share, I made some adjustments and we have it like this now;

Screen.Recording.2025-06-02.at.12.06.13.mov

[umbopepato]

LGTM! (just added a comment)

[eokoneyo]

@elasticmachine merge upstream

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 0870eca
• Cloud Deployment

Metrics [docs]

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
share	53	54	+1

Async chunks

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

id	before	after	diff
dashboard	619.1KB	620.6KB	+1.5KB
discover	1.1MB	1.1MB	+1.1KB
lens	1.5MB	1.5MB	+2.0KB
visualizations	371.9KB	373.6KB	+1.6KB
total			+6.3KB

Page load bundle

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

id	before	after	diff
lens	59.8KB	59.8KB	-3.0B
navigation	12.0KB	12.1KB	+78.0B
reporting	49.7KB	50.4KB	+746.0B
share	48.8KB	50.5KB	+1.6KB
total			+2.4KB

Unknown metric groups

API count

id	before	after	diff
share	118	120	+2

History

• 💛 Build #302419 was flaky b17875f
• 💛 Build #302277 was flaky 6091e8f
• 💔 Build #302148 failed a45d819
• 💔 Build #302075 failed ac47090
• 💔 Build #301707 failed 557e3b8

cc @eokoneyo

[eokoneyo]

Merging this in, to attend to the raised concerns in #222093

[eokoneyo]

💚 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