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

Injects bulk update allows to update irrelevant fields #2165

Open
impolitepanda opened this issue Jan 7, 2025 · 1 comment
Open

Injects bulk update allows to update irrelevant fields #2165

impolitepanda opened this issue Jan 7, 2025 · 1 comment
Labels
bug use for describing something not working as expected
Milestone

Comments

@impolitepanda
Copy link
Member

Description

Bulk update of injects always allow a user to add/replace/remove assets, asset groups, and teams, even if the selected injects are only of type email, for instance.

Environment

  1. MacOS
  2. OpenBAS version: 1.11.0 }
  3. OpenBAS client: frontend

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to scenario -> Inject tabs
  2. Either choose a scenario with at least 1 inject of type email or create one
  3. Select at least 1 email type inject.
  4. In the toolbar, click on the bulk update icon
  5. Observe that you can still add/replace/remove assets and asset groups

Expected Output

To be defined:

  • If only email type injects are selected, only allow for add/replace/remove of teams ?
  • What if there are multiple types of injects, some which don't allow assets or asset groups, some other allowing it ?
  • Warning on the fact that when using the "select all" feature, we don't have access to pages that are not loaded so we can't know on the client side if all selected elements are of a certain type or not unless a filter is set.

Actual Output

The bulk update window always allow updated of assets, asset groups or teams even if the type of inject don't allow it.
The update still works, and data is persisted in the DB, despite being useless.

Screenshots (optional)

Image

@impolitepanda impolitepanda added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jan 7, 2025
@jborozco jborozco removed the needs triage use to identify issue needing triage from Filigran Product team label Jan 8, 2025
@jborozco
Copy link

jborozco commented Jan 8, 2025

To be done:

  • Make sure assets and asset groups are not updated in the DB for non-technical injects so the filtering system will not be impacted

Out of scope:

  • Teams: we want to be able to assign teams for technical injects because we can add human response expectation to a technical inject in a simulation
  • Form interaction: no need to block the behavior in the UI if the change doesn't have an impact on the DB

@EllynBsc EllynBsc added this to the Bugs backlog milestone Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected
Projects
None yet
Development

No branches or pull requests

3 participants