Repository navigation
[ES|QL] Query History #173217
Description
Activity
Pinging @elastic/kibana-visualizations (Team:Visualizations)
@stratoula , @timductive and @MichaelMarcialis - I have updated this issue with the main user stories and details. Take a look.
Capturing some design clarifications from a Slack/EUI thread on the main 'Run query' button.
With the One Discover/ES|QL-first efforts we are also considering changes to the Run button (granted, it is earlier on).
- Andrea and I were looking to use the secondary green color to better differentiate the ES|QL mode (from the data view-oriented mode) and gain more contrast to the other primary CTA (Save).
- Design feedback on the wireframe shared above - we aligned that the shortcut could be in a tooltip, instead of inside the button
Once the EUI side of this is done (enabling overrides of the button text), we can then make the following overrides on the Kibana side:
- Keep it blue/primary for now (no change to color)
- Change the label to Run
- Show the
playicon - Show the keyboard shortcut in a (delayed) tooltip
End result for this pass:
Later, we can consider further evolving the styles (e.g. to green, maybe icon-only) as the other initiatives progress.
Reacted by Michael MarcialisPinging @elastic/kibana-esql (Team:ESQL)
- added a commit that references this issue
on Mar 28, 2024
The query history feature aims to enhance user experience in ES|QL by providing a list of recently executed queries to the user.
There are six main user stories for this MVP release of this feature, and they are described below:
Note
The query history will be available in these ES|QL editors:
Storage:
Storing successful vs errored queries:
The reason for not storing many errored queries is that many new users would have syntax errors while learning ESIQL and it would pollute the limited query history items with irrelevant items.