Jared Burgett
Jared Burgett
@muskangulati-qasource yes, the labels look appropriate. If you'd like to test the functionality, you should be able to do so in Serverless!
š Hi @arvindersingh-qasource ! The above functionality is expected, as `unknown_impact` is indeed an invalid assignment. What is now available in Serverless is `unassigned_impact`. See below screenshot for an example:...
@abhishekbhatia1710 can you please have a look at the above, to see if this new `unassigned_impact` functionality should be available in Serverless?
Will have a team member look at this test. However, for external communication purposes, this test specific failing should not be a blocker on Serverless promotion, because the legacy risk...
@mistic yes, please feel free to skip for now if this is preventing promotion
Hey @rayafratkina ! Per the conversation above, I mentioned that this was less of a priority from our side due to this legacy feature not being relevant for serverless. Since...
First stop-gap: https://github.com/elastic/kibana/pull/195651
This is a higher priority due to the Serverless release upcoming, will assess.
Tested and confirmed that this problem does not yet exist in Serverless, because the Entity Store is completely unavailable in Serverless, and the dashboard view correctly shows the Risk Enablement....