Open sukhwindersingh-qasource opened 10 months ago
Pinging @elastic/security-solution (Team: SecuritySolution)
@manishgupta-qasource Kindly review this Thanks !
Reviewed and assigned to @MadameSheema
Pinging @elastic/security-threat-hunting (Team:Threat Hunting)
Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)
This makes sense as the timeline had not been saved yet. @janmonschke, do you think we should disable certain actions until we can verify the timeline has been saved? Thanks!
This makes sense as the timeline had not been saved yet. @janmonschke, do you think we should disable certain actions until we can verify the timeline has been saved? Thanks!
Chiming in as I fixed a similar bug (PR) a few weeks ago where users could favorite an unsaved timeline. I decided to prevent users from favoriting until the timeline would be saved. I feel like we need to be consistent as much as possible
This makes sense as the timeline had not been saved yet. @janmonschke, do you think we should disable certain actions until we can verify the timeline has been saved? Thanks!
Yep, that would make sense
@janmonschke , Do you remember if you already worked on this bug?
@logeekal I did not work on this yet, iirc
Describe the bug: User is able to attach a duplicate timeline to a Case without Saving the timeline
Kibana/Elasticsearch Stack version
VERSION: 8.12.0 BC5 BUILD: 70053 COMMIT: db9b8921b37139cbb1e11d23f6381f655edeb72b
Browser and Browser OS Version: Firefox for windows OS Version: 121.0
Elastic Endpoint Version: N/A
Original install method: None
Functional Area: Timeline
Initial Setup:
Precondition
Steps to reproduce
Actual Result :
Expected Result :
Additional Information
no timeline id found
Screen-Cast :
https://github.com/elastic/kibana/assets/108654988/5e83bc9f-e569-445d-8a1a-97bf786c0e5a