Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[Cases] Handle lens actions in Serverless #163581
[Cases] Handle lens actions in Serverless #163581
Changes from 11 commits
8c2a2e2
b803cd8
00abb4a
967d6f0
ce954dc
fdbd3aa
5b18d96
de5e9b6
36b78b2
0d33bca
72ed819
9972f69
6ec2f43
e5393ab
521b5f1
271f5d8
a68df43
0b9f944
83da2f6
fb9a42c
5bae788
20516f1
437e01c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 think this will slightly change the behavior of the form when going through Analytics in Classic Kibana.
There there is no
owner
and theavailableOwners
can be 1(depending on the role's permissions). This will make it not show the owner picker(your PR) vs showing the owner picker with all options disabled except one(main).It is a specific scenario so maybe it is not a problem.
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.
hmm..The only way to handle this could be to add another config variable which tells weather it is serverless or classic kibana and then put the check accordingly.
However I think it's
okay to not show owner selector picker when only one owner
because we don't show it anyway when it's a security solution dashboard and user has permission for cases in security in classic kibana.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.
Yeah but there we don't show because we are in Security Solution. The owner is defined and it is safe to assume the created case will end up inside Security Solution.
In the scenario I mentioned, we start from
Analytics
. The user has no indication of where the case will end up.(Although he can assume if he only has access to like, Observability 😄 )
I think this is minor though. Maybe double-check with @mdefazio ?
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'm good with hiding this if there is only one solution available. Thanks for double checking on this. @shanisagiv1 Let me know if you're ok with hiding this solution selector (and if you would like some more context to this, happy to zoom 😉 )