-
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
[ResponseOps][Cases] Get reporters and tags by aggregation #123362
Conversation
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
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.
Left a few comments about sorting, and I would reach out to Larry as we discussed about what to do with the ensureSavedObject...
calls.
@@ -74,17 +74,17 @@ export default ({ getService }: FtrProviderContext): void => { | |||
for (const scenario of [ | |||
{ | |||
user: globalRead, | |||
expectedTags: ['sec', 'obs'], | |||
expectedTags: ['obs', 'sec'], |
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.
Let's try adding a sort to the aggregation to see if we can get the sorting consistent:
"order": { "_key": "asc" }
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 added the _key
. I am gonna leave the change of order of values in the tests as obs
preceding sec
alphabetically.
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @cnasikas |
Summary
Fixes: #98126
Checklist
Delete any items that are not applicable to this PR.
For maintainers