Skip to content
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

[Security Solution] [Bug] The user is not able to exit the full screen for session viewer #205126

Open
muskangulati-qasource opened this issue Dec 24, 2024 · 7 comments
Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team v8.18.0

Comments

@muskangulati-qasource
Copy link

Describe the bug
The user is not able to exit the full screen for session viewer

Kibana/Elasticsearch Stack version

VERSION: 8.18.0
BUILD: 81228
COMMIT: 9d6cc0792e538a076d68ffcfabbf6551912fb24e

Pre Conditions

  1. Kibana v8.18.0 build be must be available

Steps

  1. Kibana version 8.18.0 or above should exist
  2. A few session alerts for Linux should exist
  3. Navigate to the Alerts tab and click on full screen for the alerts tab
  4. Click on session viewer for any alert
  5. Click on the full screen button
  6. Observe, the user is not able to exit the full screen for the same

Expected Result
The user should be able to exit the full screen for session viewer

Screen Recording

sessionFullScreenError.mp4
@muskangulati-qasource muskangulati-qasource added bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed labels Dec 24, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@muskangulati-qasource muskangulati-qasource added impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. v8.18.0 labels Dec 24, 2024
@muskangulati-qasource
Copy link
Author

@arvindersingh-qasource please review!

@arvindersingh-qasource
Copy link

Reviewed and Assigned to @MadameSheema @banderror

@MadameSheema
Copy link
Member

@arvindersingh-qasource @muskangulati-qasource please ping @banderror just for prebuilt custom rules bugs.

@MadameSheema MadameSheema removed their assignment Dec 24, 2024
@MadameSheema MadameSheema added the Team:Threat Hunting:Investigations Security Solution Investigations Team label Dec 24, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

@MadameSheema MadameSheema added the Team:Threat Hunting Security Solution Threat Hunting Team label Dec 24, 2024
@MadameSheema
Copy link
Member

On 8.18.0 the plan is for the session view to be part of the alert flyout so the full screen functionality is not going to exist anymore.

@PhilippeOberti
Copy link
Contributor

On 8.18.0 the plan is for the session view to be part of the alert flyout so the full screen functionality is not going to exist anymore.

Like @MadameSheema said, we can keep this ticket opened for now, but we will not fix this, as Session View is not going to have a full screen mode pretty soon. We're indeed moving it to the expandable flyout

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team v8.18.0
Projects
None yet
Development

No branches or pull requests

6 participants