Skip to content

[Security Solution] The status after releasing shows 'Isolated' whereas it should show 'released' #104295

@muskangulati-qasource

Description

@muskangulati-qasource

Description:
The status after releasing shows 'Isolated' whereas it should show 'released'

Build Details:

VERSION: 7.14.0 BC1
BUILD: 42292
COMMIT: 071a74e02f82b79a4a10026b5c9e02d593112fd4
ARTIFACT: https://staging.elastic.co/7.14.0-8eba2f5f/summary-7.14.0.html

Browser Details:
All

Preconditions:

  1. Kibana user should be logged in.
  2. Endpoint should be deployed

Steps to Reproduce:

  1. Navigate to the Endpoint Tab
  2. Isolate the host
  3. After some time, release the host
  4. Observe that after the 'releasing' status, the status starts showing 'isolated'.

Impacted Test case:
N/A

Actual Result:
The status after releasing shows 'Isolated' whereas it should show 'released'

Expected Result:
The status after releasing should show 'released'

What's working:
N/A

What's not working:
N/A

Screen Recording:

IsolationStatus.mp4

Logs:
N/A

Metadata

Metadata

Assignees

Labels

OLM SprintQA:ValidatedIssue has been validated by QATeam: SecuritySolutionSecurity Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.Team:Defend Workflows“EDR Workflows” sub-team of Security SolutionbugFixes for quality problems that affect the customer experienceimpact:highAddressing this issue will have a high level of impact on the quality/strength of our product.v7.14.0

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions