-
Notifications
You must be signed in to change notification settings - Fork 909
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] [Data Explore] scope history on legacy discover plugin is broken #4698
Comments
Pulled down the latest change from the feature branch, now the save search window works as expected. |
However, i think there is another bug related to this: in one functional test, it saved a saved search first on discover, then navigate to dashboard page to add that saved search to the dashboard, and save the dashboard. Then go back to discover page by clicking the discover tab in the side menu. It should directly go back to that saved search page, so then when we make modifications, the save window will show the save as new toggle. However, now in the legacy discover, the scope history seem to be lost, and clicking the discover tab in the side menu wont take us to the saved search page anymore, it will only take us to the general discover page. Thus now when we click save, the save window will not show save as new toggle, cuz it thinks this is a new saved search. @ashwin-pc In previous discover: Screen.Recording.2023-08-09.at.10.37.19.PM.movIn the current legacy discover: Screen.Recording.2023-08-09.at.10.42.28.PM.mov |
Since legacy discover will be removed in 2.11, this issue wont be fixed. |
Describe the bug
The save window on legacy discover plugin is not the same as previous one, the current one does not allow save as new toggle, and is causing some function tests to fail. Therefore, we can never edit and save an existing saved search, it always ends up saving a new saved search.
Current one:
Expected one/previous one:
The text was updated successfully, but these errors were encountered: