Clicking new on discover while in ES|QL view creates a temporary dataview in NON ESQL mode

[bhavyarm]

Kibana version: 8.13.0 snapshot

Browser version: chrome latest

Browser OS version: OS X

Original install method (e.g. download page, yum, from source, etc.): from snapshots

Describe the bug: If you click new when you are in ES|QL view, Kibana exits out of ES|QL view to non-ES|QL view and creates a temporary dataview of the same dataview you had in ES|QL mode. This is confusing because user doesn't know this is happening and can do all the operations on the temp dataview in discover.

https://github.com/elastic/kibana/assets/7074629/d0656465-6c5b-4756-bb38-99b2c9f451e2

[elasticmachine]

Pinging @elastic/kibana-visualizations (Team:Visualizations)

[bhavyarm]

cc @stratoula

[elasticmachine]

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

[kertal]

We discussed in the team, and clicking on New should not switch to data view mode, it should stay in ES|QL mode and show the default query with the most recent index pattern as source.

[stratoula]

Yes this makes sense Matthias, can you explain me this though?

the default query with the most recent index pattern as source.

You mean, if the last query was from foo .... and then the user clicked New, navigate to New with from foo | limit 10 ?

[kertal]

You mean, if the last query was from foo .... and then the user clicked New, navigate to New with from foo | limit 10 ?

Yes, I think this would make sense

[stratoula]

Yes sounds as a great plan!