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.

Sign up for GitHub

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

Jump to bottom

[Security Solution] Importing timelines with dataViewId does not give an error. #209251

Open
logeekal opened this issue Feb 3, 2025 · 2 comments
Open

[Security Solution] Importing timelines with dataViewId does not give an error. #209251

logeekal opened this issue Feb 3, 2025 · 2 comments
Assignees
@logeekal
Labels
bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team

Comments

@logeekal
Copy link
Contributor

logeekal commented Feb 3, 2025

Describe the bug:
Importing timelines with extra field dataViewId from UI does not result in an error. It should because dataViewId is not available in Saved object mapping.

Kibana/Elasticsearch Stack version:
7.17.26

Steps to reproduce:

fakeimport_timelines.zip

  1. Unzip above file and extract the ndjson.
  2. Go to the Timelines UI
  3. Importing the mentioned ndjson should demonstrate the issue.

Current behavior:
Timelines with extra fields get imported successfully.

Expected behavior:
Timelines with extra fields should display an error.

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context (logs, chat logs, magical formulas, etc.):
@logeekal logeekal 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 Feb 3, 2025
@elasticmachine
Copy link
Contributor

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

@logeekal logeekal added the Team:Threat Hunting:Investigations Security Solution Investigations Team label Feb 3, 2025
@elasticmachine
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@logeekal logeekal

Labels
bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@logeekal @elasticmachine @PhilippeOberti