[Cases] Handle lens actions in Serverless

[js-jankisalvi]

Summary

fixes #160126

This PR

• hides owner selection while adding lens to case from dashboard for observability and securitySolution serverless
• hides add to new case and add to existing case lens action for Elasticsearch serverless

How to test

• Run Observability/Securtiy solution serverless project and add lens visualization to case from dashboard
• Run ES serverless project and check that lens do not have option to add to case
• Classic kibana works as before (check dashboard from securitySolution and generic dashboard as well)

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[elasticmachine]

Pinging @elastic/response-ops-cases (Feature:Cases)

[adcoelho]

Tested a bunch of scenarios:

• Serverless
  • Observability:
    • Does not display owner selection
    • Creates the case without errors
    • Created case has 'observability' as owner
  • Security Solution:
    • Does not display owner selection
    • Creates the case without errors
    • Created case has 'securitySolution' as owner
  • Stack:
    • Hides the options add to new case and add to existing case
• Classic Kibana
  • Still works as expected 👍

[adcoelho]

I think this will slightly change the behavior of the form when going through Analytics in Classic Kibana.

There there is no owner and the availableOwners 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.

[js-jankisalvi]

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.

[adcoelho]

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 ?

[mdefazio]

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 😉 )

[adcoelho]

Good stuff 👌

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 437e01c

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
cases	421.7KB	421.7KB	+59.0B

History

• 💛 Build #149962 was flaky 5bae788
• 💚 Build #149691 succeeded 0b9f944
• 💔 Build #149532 failed 271f5d8
• 💔 Build #149514 failed 521b5f1
• 💔 Build #149299 failed e5393ab
• 💔 Build #149202 failed 72ed819

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @js-jankisalvi