Skip to content
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

[Search Sessions] Saved object can be created even if courier:batchSearches is enabled #104311

Closed
flash1293 opened this issue Jul 5, 2021 · 1 comment · Fixed by #105407
Closed
Assignees
Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:medium Medium Level of Effort

Comments

@flash1293
Copy link
Contributor

Kibana version: 7.14

Describe the bug: It's possible to "save" a session even if courier:batchSearches is enabled which effectively disables the whole async search process.

Steps to reproduce:

  1. Set courier:batchSearches in advanced settings
  2. Go to Discover
  3. Save the session
  4. Go to session management
  5. Sasved session with 0 searches "in progress" is shown

Expected behavior:
It shouldn't be possible to save the session

Screenshots (if relevant):
Screenshot 2021-07-05 at 16 46 05

@flash1293 flash1293 added bug Fixes for quality problems that affect the customer experience Team:AppServices labels Jul 5, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServices)

@lizozom lizozom changed the title Search session can be created even if courier:batchSearches is enabled [Search Sessions] Saved object can be created even if courier:batchSearches is enabled Jul 6, 2021
@lizozom lizozom added impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. impact:critical This issue should be addressed immediately due to a critical level of impact on the product. loe:small Small Level of Effort and removed impact:critical This issue should be addressed immediately due to a critical level of impact on the product. labels Jul 6, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Jul 6, 2021
@Dosant Dosant self-assigned this Jul 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:medium Medium Level of Effort
Projects
None yet
4 participants