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

[Cases][Timeline] Saved Object Type Conversion #105677

Closed
8 tasks done
jonathan-buttner opened this issue Jul 14, 2021 · 6 comments
Closed
8 tasks done

[Cases][Timeline] Saved Object Type Conversion #105677

jonathan-buttner opened this issue Jul 14, 2021 · 6 comments
Assignees
Labels
epic Feature:Cases Cases feature Feature:Timeline Security Solution Timeline feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team:Threat Hunting Security Solution Threat Hunting Team v7.16.0

Comments

@jonathan-buttner
Copy link
Contributor

jonathan-buttner commented Jul 14, 2021

As part of the effort to make saved objects shareable across multiple spaces we need to make a few changes to how Cases and Timeline interacts with the saved objects. This is required because in 8.0 the kibana core team is changing how the internal saved object id value is being stored to support being shared across multiple spaces.

The meta ticket for the core team is here: #100489.

The first thing is to migrate any of our foreign key fields (fields that reference another saved object's id field) to the references field. After this migration is complete we need to switch our usage of the saved object get API to use resolve instead as noted in the meta ticket above.

The tasks associated with this work are the following:

@jonathan-buttner jonathan-buttner added Team:Threat Hunting Security Solution Threat Hunting Team Feature:Timeline Security Solution Timeline feature Feature:Cases Cases feature labels Jul 14, 2021
@jonathan-buttner jonathan-buttner self-assigned this Jul 14, 2021
@elasticmachine
Copy link
Contributor

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

@jportner
Copy link
Contributor

In case anyone is following this issue but not the linked meta-issue (#100489):

I published the Sharing Saved Objects developer guide, please take a look before proceeding with the implementation. And of course, please reach out if you run into any problems!

@stephmilovic
Copy link
Contributor

Heads up, I'm adding a new reference to the Kibana data view saved object (index-pattern) on the timeline saved object as part of this work https://github.com/elastic/security-team/issues/772

@jportner
Copy link
Contributor

jportner commented Oct 1, 2021

Chat today mapping the steps in the Sharing Saved Objects dev guide to each SO type:

Step 1 Step 2 Step 3 Step 4
cases #107561 #110854 #110854 PR #113552
cases-comments N/A N/A N/A PR #113552
cases-configure #107561 N/A N/A PR #113552
cases-connector-mappings N/A N/A N/A PR #113552
cases-sub-case N/A N/A N/A PR #113552
cases-user-actions #109177 N/A N/A PR #113552
siem-ui-timeline #110863 #110862 #110862 PR #113552
siem-ui-timeline-note #110863 N/A N/A PR #113552
siem-ui-timeline-pinned-event #110863 N/A N/A PR #113552

@jonathan-buttner if you could take a look at the above and make sure I didn't miss anything, that would be great! feel free to just edit this comment if you need to add any links.

@jonathan-buttner
Copy link
Contributor Author

@jportner yep that looks good 👍

@cnasikas cnasikas added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Jan 10, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Feature:Cases Cases feature Feature:Timeline Security Solution Timeline feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team:Threat Hunting Security Solution Threat Hunting Team v7.16.0
Projects
None yet
Development

No branches or pull requests

8 participants