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][Epic] Improve how plugins consumes the "attach to a case" functionality #123183

Closed
11 tasks done
cnasikas opened this issue Jan 17, 2022 · 2 comments
Closed
11 tasks done
Assignees
Labels
8.2 candidate considered, but not committed, for 8.2 release Feature:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v8.2.0

Comments

@cnasikas
Copy link
Member

cnasikas commented Jan 17, 2022

Cases plugin provides a flyout and a modal for other plugins to be able to attach data to a case. At the moment, plugins need to keep the state of opening/closing the modal or the flyout and know the internals of how to attach the data to the cases. Cases should provide an out-of-the-box solution where plugins with minimal configuration can use the feature of attaching data to a case. Cases should:

  • Keep the state opening/closing of the flyout or the modal internally
  • Provide attach to case buttons that can be used in a context menu or a custom UI
  • Allow plugins to pass the data they want to attach to a case.

Proposal by @semd

Cases can export an add-to-case context where the consumer plugins can use along with the add-to-case buttons. For example:

<AddToCasesContext>
   <ConsumerPlugin>
        ...
   		<AddToCase attachments=[ { alerts: [{ id: 'test-id', index: '.test-index' }] }] />
   </ConsumerPlugin>
</AddToCasesContext>

Issues:

Meta: #123310

@cnasikas cnasikas added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Cases Cases feature v8.2.0 labels Jan 17, 2022
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

@cnasikas cnasikas added the 8.2 candidate considered, but not committed, for 8.2 release label Jan 19, 2022
@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
@academo academo changed the title [Cases] Improve how plugins consumes the "attach to a case" functionality [Cases][Epic] Improve how plugins consumes the "attach to a case" functionality Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.2 candidate considered, but not committed, for 8.2 release Feature:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v8.2.0
Projects
None yet
Development

No branches or pull requests

4 participants