Enhancement: Change a dashboard panel's timefield on the fly

[rseldner]

Describe the feature:
Change a dashboard panel's timefield on the fly

Describe a specific use case for the feature:

It would be nice to be able to edit the timefield of an individual panel on the fly.

The data behind a visualization can have multiple date fields.
Sometimes users need to visualization based on these addition date fields, but the timefield of a visualization is fixed to what is set on the source data view. So to currently accommodate this, a user would need to either:

• Edit the timefield of a data view - This can be undesireable as it could potentially impact other panels where the change is not needed/relevant. The user might not even have the required privileges.
• Create multiple data views of the same data with unique timefields - This is cumbersome and would still involve having to edit the visualization's data view, which is impractical.

Mockup:

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[Heenawter]

This will be possible with ES|QL controls - closing in favour of #134706 for now. cc @ghudgins

[rseldner]

This will be possible with ES|QL controls

@Heenawter 👋 Will such controls apply to all panel types or strictly ESQL panels? Can't quite tell in ESQL Control's PR example: #202875

Won't the controls apply to all panels on a dashboard? The request here is for users to be able to change it per panel.
I see a way around that would be to add the tstart and tend parameters to a viz; however, changing the ESQL syntax requires actually editing the dashboard/visualization, which would require privileges dashboard users may/should not have.

[Heenawter]

Will such controls apply to all panel types or strictly ESQL panels?

They will only apply to ES|QL panels.

Won't the controls apply to all panels on a dashboard?

Nope! :) The idea behind ES|QL controls is that you will create an ES|QL variable that can be used in individual panels - when a control is created on that variable, then only the panels that use that variable will be impacted by changes to that control. This will be maniputable by a user, even if they do not have edit privileges for dashboard and/or relevant visualizations.

[rseldner]

They will only apply to ES|QL panels.

Making the switch will be very cumbersome for large environments, unless we will be introducing a way to switch existing panels from Lens to ESQL.

Nope! :) The idea behind ES|QL controls is that you will create an ES|QL variable that can be used in individual panels - when a control is created on that variable, then only the panels that use that variable will be impacted by changes to that control. This will be maniputable by a user, even if they do not have edit privileges for dashboard and/or relevant visualizations.

Thanks you, that aspect of it sounds promising.