-
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
[Uptime] Overview link to Exploratory View should not filter by monitor #122907
[Uptime] Overview link to Exploratory View should not filter by monitor #122907
Conversation
Pinging @elastic/uptime (Team:uptime) |
This is now ready for review. |
f4eeef4
to
4bec0d1
Compare
@elasticmachine merge upstream |
/* | ||
* The second condition exists because we don't want to link users to an | ||
* exploratory view that is filtered by a specific monitor when they're on | ||
* the Uptime Overview page. | ||
* | ||
* This condition is intended to allow monitor filtering on all other pages. | ||
*/ |
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.
Comment is helpful but seems unnecessary :)
I think code is self explanatory, No?
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.
I was on the fence about it. I told myself if the reviewer mentioned it I'd delete it 😉
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.
Done baa460e.
…er on exploratory view link.
7b7b521
to
baa460e
Compare
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
💔 All backports failed
How to fixRe-run the backport manually:
Questions ?Please refer to the Backport tool documentation |
…or (elastic#122907) * Modify Exploratory View link to prevent filtering by monitor from Overview page. * Modify route match so only detail page will include monitor name filter on exploratory view link. * Remove unnecessary comment. (cherry picked from commit 939a642)
…or (elastic#122907) * Modify Exploratory View link to prevent filtering by monitor from Overview page. * Modify route match so only detail page will include monitor name filter on exploratory view link. * Remove unnecessary comment. (cherry picked from commit 939a642)
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
…y monitor (#122907) (#123268) * [Uptime] Overview link to Exploratory View should not filter by monitor (#122907) * Modify Exploratory View link to prevent filtering by monitor from Overview page. * Modify route match so only detail page will include monitor name filter on exploratory view link. * Remove unnecessary comment. (cherry picked from commit 939a642) * Fix `cherry-pick` error. * Fix merge errors. Co-authored-by: Kibana Machine <[email protected]>
Summary
Resolves #121348.
The Overview page should no longer filter the Exploratory View by monitor name when the link is clicked.
Testing this PR
Follow the steps in the linked issue. When running this branch you should see that the exploratory view link that the page generates does not contain a monitor-specific filter on the overview page. This monitor filtering should work on other pages.Repeat these same steps with the certs view. Start on the overview page, drill in, then go to certs and link to exp. view.
Ensure that when clicking from the detail page of a monitor, the exp. view is still filtered by monitor.
Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers