## Summary

Failing Security cypress tests on main. Skipping to unblock and @elastic/security-detections-response-rules will investigate and unskip.

Example failure: https://buildkite.com/elastic/kibana-pull-request/builds/108068

(cherry picked from commit 40728e5)

… (#151247)

# Backport

This will backport the following commits from `main` to `8.7`:
- [[Security Solution] Skips failing cypress tests on main
(#151244)](#151244)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Garrett
Spong","email":"spong@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-02-15T03:48:59Z","message":"[Security
Solution] Skips failing cypress tests on main (#151244)\n\n##
Summary\r\n\r\nFailing Security cypress tests on main. Skipping to
unblock and @elastic/security-detections-response-rules will investigate
and unskip.\r\n\r\nExample failure:
https://buildkite.com/elastic/kibana-pull-request/builds/108068","sha":"40728e5c4854492996e8243734732e9d2b738460","branchLabelMapping":{"^v8.8.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection
Rules","v8.7.0","v8.8.0"],"number":151244,"url":"https://github.com/elastic/kibana/pull/151244","mergeCommit":{"message":"[Security
Solution] Skips failing cypress tests on main (#151244)\n\n##
Summary\r\n\r\nFailing Security cypress tests on main. Skipping to
unblock and @elastic/security-detections-response-rules will investigate
and unskip.\r\n\r\nExample failure:
https://buildkite.com/elastic/kibana-pull-request/builds/108068","sha":"40728e5c4854492996e8243734732e9d2b738460"}},"sourceBranch":"main","suggestedTargetBranches":["8.7"],"targetPullRequestStates":[{"branch":"8.7","label":"v8.7.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.8.0","labelRegex":"^v8.8.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/151244","number":151244,"mergeCommit":{"message":"[Security
Solution] Skips failing cypress tests on main (#151244)\n\n##
Summary\r\n\r\nFailing Security cypress tests on main. Skipping to
unblock and @elastic/security-detections-response-rules will investigate
and unskip.\r\n\r\nExample failure:
https://buildkite.com/elastic/kibana-pull-request/builds/108068","sha":"40728e5c4854492996e8243734732e9d2b738460"}}]}]
BACKPORT-->

Co-authored-by: Garrett Spong <spong@users.noreply.github.com>

## Summary

Failing Security cypress tests on main. Skipping to unblock and @elastic/security-detections-response-rules will investigate and unskip.

Example failure: https://buildkite.com/elastic/kibana-pull-request/builds/108068

**Relates to:** #151244

## Summary

Re-enable `Do not clears kql when navigating to a new page` url state e2e test.

## Details

Investigation has shown that #150787 lead to breaking this test. While it's not clear from the EUI upgrade PR itself the cause lays under the hood. It fixes retrieving the state (current KQL) from the url. As the test visits the page with the saved KQL which is properly restored the next `kqlSearch()` command types the same KQL in the query bar leading to invalid KQL and broken test eventually. For some reason the KQL wasn't able to restore on this page while it's not an issue anymore I removed `kqlSearch()` command and fixed the test this way.

…52075)

**Relates to:** elastic#151244

## Summary

Re-enable `Do not clears kql when navigating to a new page` url state e2e test.

## Details

Investigation has shown that elastic#150787 lead to breaking this test. While it's not clear from the EUI upgrade PR itself the cause lays under the hood. It fixes retrieving the state (current KQL) from the url. As the test visits the page with the saved KQL which is properly restored the next `kqlSearch()` command types the same KQL in the query bar leading to invalid KQL and broken test eventually. For some reason the KQL wasn't able to restore on this page while it's not an issue anymore I removed `kqlSearch()` command and fixed the test this way.

(cherry picked from commit 5514f93)

…2075) (#152423)

# Backport

This will backport the following commits from `main` to `8.7`:
- [[Security Solution] Re-enable a skipped url state e2e test
(#152075)](#152075)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Maxim
Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2023-03-01T09:04:31Z","message":"[Security
Solution] Re-enable a skipped url state e2e test (#152075)\n\n**Relates
to:** https://github.com/elastic/kibana/pull/151244\r\n\r\n##
Summary\r\n\r\nRe-enable `Do not clears kql when navigating to a new
page` url state e2e test.\r\n\r\n## Details\r\n\r\nInvestigation has
shown that #150787 lead to
breaking this test. While it's not clear from the EUI upgrade PR itself
the cause lays under the hood. It fixes retrieving the state (current
KQL) from the url. As the test visits the page with the saved KQL which
is properly restored the next `kqlSearch()` command types the same KQL
in the query bar leading to invalid KQL and broken test eventually. For
some reason the KQL wasn't able to restore on this page while it's not
an issue anymore I removed `kqlSearch()` command and fixed the test this
way.","sha":"5514f93fc8ecccc007d1e25c9413df1c739feae9","branchLabelMapping":{"^v8.8.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection
Rules","backport:prev-minor","v8.7.0","v8.8.0"],"number":152075,"url":"https://github.com/elastic/kibana/pull/152075","mergeCommit":{"message":"[Security
Solution] Re-enable a skipped url state e2e test (#152075)\n\n**Relates
to:** https://github.com/elastic/kibana/pull/151244\r\n\r\n##
Summary\r\n\r\nRe-enable `Do not clears kql when navigating to a new
page` url state e2e test.\r\n\r\n## Details\r\n\r\nInvestigation has
shown that #150787 lead to
breaking this test. While it's not clear from the EUI upgrade PR itself
the cause lays under the hood. It fixes retrieving the state (current
KQL) from the url. As the test visits the page with the saved KQL which
is properly restored the next `kqlSearch()` command types the same KQL
in the query bar leading to invalid KQL and broken test eventually. For
some reason the KQL wasn't able to restore on this page while it's not
an issue anymore I removed `kqlSearch()` command and fixed the test this
way.","sha":"5514f93fc8ecccc007d1e25c9413df1c739feae9"}},"sourceBranch":"main","suggestedTargetBranches":["8.7"],"targetPullRequestStates":[{"branch":"8.7","label":"v8.7.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.8.0","labelRegex":"^v8.8.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/152075","number":152075,"mergeCommit":{"message":"[Security
Solution] Re-enable a skipped url state e2e test (#152075)\n\n**Relates
to:** https://github.com/elastic/kibana/pull/151244\r\n\r\n##
Summary\r\n\r\nRe-enable `Do not clears kql when navigating to a new
page` url state e2e test.\r\n\r\n## Details\r\n\r\nInvestigation has
shown that #150787 lead to
breaking this test. While it's not clear from the EUI upgrade PR itself
the cause lays under the hood. It fixes retrieving the state (current
KQL) from the url. As the test visits the page with the saved KQL which
is properly restored the next `kqlSearch()` command types the same KQL
in the query bar leading to invalid KQL and broken test eventually. For
some reason the KQL wasn't able to restore on this page while it's not
an issue anymore I removed `kqlSearch()` command and fixed the test this
way.","sha":"5514f93fc8ecccc007d1e25c9413df1c739feae9"}}]}] BACKPORT-->

Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>

…52075)

**Relates to:** elastic#151244

## Summary

Re-enable `Do not clears kql when navigating to a new page` url state e2e test.

## Details

Investigation has shown that elastic#150787 lead to breaking this test. While it's not clear from the EUI upgrade PR itself the cause lays under the hood. It fixes retrieving the state (current KQL) from the url. As the test visits the page with the saved KQL which is properly restored the next `kqlSearch()` command types the same KQL in the query bar leading to invalid KQL and broken test eventually. For some reason the KQL wasn't able to restore on this page while it's not an issue anymore I removed `kqlSearch()` command and fixed the test this way.