-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[QA][refactor] Use ui settings - sample data #114530
Conversation
buildkite, test this |
buildkite, test this |
1 similar comment
buildkite, test this |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
b65677b
to
f5cb610
Compare
Use ui settings instead of setting absolute range for timepicker. Stack this pr on top of: #114530 ...to use the new common page time fns.
Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530
f5cb610
to
69cfacc
Compare
Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530
Use ui settings instead of setting absolute range for timepicker. Stack this pr on top of: #114530 ...to use the new common page time fns.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as long as Jenkins passes.
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
💔 Backport failed
To backport manually run: |
# Conflicts: # test/functional/page_objects/common_page.ts
Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530
Use ui settings instead of setting absolute range for timepicker. Stack this pr on top of: #114530 ...to use the new common page time fns.
Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530
Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530
Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530
Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530
Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530
Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530
Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530
Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530
* [QA][refactor] Use ui settings - discover histogram Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530 * Use TimeStrings interface.
* [QA][refactor] Use ui settings - discover histogram Use ui settings instead of setting absolute range for timepicker. Stacked on top of: elastic#114530 * Use TimeStrings interface.
* [QA][refactor] Use ui settings - discover histogram Use ui settings instead of setting absolute range for timepicker. Stacked on top of: elastic#114530 * Use TimeStrings interface.
* [QA][refactor] Use ui settings - discover histogram Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530 * Use TimeStrings interface. Co-authored-by: Tre <[email protected]>
* [QA][refactor] Use ui settings - discover histogram Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530 * Use TimeStrings interface. Co-authored-by: Tre <[email protected]>
* [QA][refactor] Use ui settings - discover histogram Use ui settings instead of setting absolute range for timepicker. Stacked on top of: #114530 * Use TimeStrings interface.
[skip-ci]
Use ui settings instead of setting absolute range
for timepicker.
Add 2 time functions to the common page,
set the time, unset the time.
The user handles their own navigation.
Helps with: #113998