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

[RAM] UX: Bulk editing rules #136017

Open
mdefazio opened this issue Jun 24, 2022 · 4 comments
Open

[RAM] UX: Bulk editing rules #136017

mdefazio opened this issue Jun 24, 2022 · 4 comments
Assignees
Labels
Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mdefazio
Copy link
Contributor

mdefazio commented Jun 24, 2022

Summary

Provide the ability to perform bulk actions on a [large] set of rules.

Beginning list of actions:

  • Delete
  • Enable / Disable
  • Modify tags

Future (TBD):

  • Modify connectors/actions?
  • Modify run schedule (Run interval/check every, Notify on change)?

Links

Whimsical wireframes

image


Above flows reference the Content Management project to maintain consistency. This is a divergence from Security's flows that rely solely on the popover from bulk edit menu above the table and a corresponding flyout. (Security's bottom timeline bar prohibits the above flow currently)

@mdefazio mdefazio self-assigned this Jun 24, 2022
@mdefazio mdefazio transferred this issue from another repository Jul 8, 2022
@mdefazio mdefazio added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Jul 8, 2022
@elasticmachine
Copy link
Contributor

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

@mdefazio
Copy link
Contributor Author

mdefazio commented Jul 8, 2022

@XavierM Can you take a look and make sure this all makes sense. Ideally we won't be creating anything unique here as this should be the flow for this type of content management going forward.

@emma-raffenne
Copy link
Contributor

@maciejforcone FYI

@mdefazio
Copy link
Contributor Author

Just mentioning again the work happening from the Content Management project for bulk editing. My understanding is the result of that will provide solutions an easy way to adopt the pattern. Hopefully avoiding any duplicate work on our side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

3 participants