[Security Solution]When user have unsaved timeline then the alerts flyout doesn't close on navigation to other pages.

[sukhwindersingh-qasource]

Describe the bug:

• When user have unsaved timeline then the alerts flyout doesn't close on navigation to other pages.

Kibana/Elasticsearch Stack version

VERSION: 8.14.0
BUILD: 73762
COMMIT: 2a492e1625f24336f3259b2b8df62b2b18127e81

Browser and Browser OS Version: Firefox for windows OS Version: 122.0 (64-bit)

Chrome for windows OS Version: 1Version 123.0.6312.105 (64-bit)

Elastic Endpoint Version:

• N/A

Original install method:

• None

Functional Area:

• Alert flyout

Initial Setup:

• None

Precondition

• User should have unsaved timeline present

Steps to reproduce

• Navigates to Alerts tab.
• Now click on the Alert details icon of any alert
• Now navigate to another page lets say manage.
• Observe the alerts flyout doesn't close on navigation to other pages.

Current Result

• When user have unsaved timeline then the alerts flyout doesn't close on navigation to other pages.

Expected Result

• When user have unsaved timeline then the alerts flyout should close on navigation to other pages.

Screen-cast

https://github.com/elastic/kibana/assets/108654988/37e151a7-06d4-42d9-8a76-b09d1084fe0d

[elasticmachine]

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

[sukhwindersingh-qasource]

@karanbirsingh-qasource Kindly review this

Thanks!

[PhilippeOberti]

@sukhwindersingh-qasource hmmm that's a very interesting bug... It seems very unlikely that the flyout staying open would be related to a Timeline existing and being unsaved, as the 2 don't really have much in common in the code...

Actually trying this locally I cannot reproduce the issue:

https://github.com/elastic/kibana/assets/17276605/25084533-a741-4ece-ad2e-78f76f9b5492

Let's see what @karanbirsingh-qasource finds when he tests this!

[karanbirsingh-qasource]

Hi @PhilippeOberti

Yes I am able to reproduce the issue, just checked in your shared video on moving to other page you didn't received the modal for timeline Unsaved Changed .

Build Details:

Version : 8.14 BC3
Commit: 2a492e1625f24336f3259b2b8df62b2b18127e81
Build: 73762

so can you perform this steps once again

• instead of investigate in timeline operation perform add to timeline action on any value from alert table ( this specific action is causing this issue )

• open alert Flyout
• Navigate to other page of security app
• then you will get the unsaved changed modal and after that click on confirm option
• you will observe the alert Flyout remained in opened state

hope you this steps will help reproducing the issue.

[PhilippeOberti]

Ok got it! This is a really weird one. Thanks for providing the details to reproduce locally! I will be taking a look!

[elasticmachine]

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

[elasticmachine]

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