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

Mass selection with the shift key does not work on Incident #6283

Closed
Lhorus6 opened this issue Mar 7, 2024 · 2 comments · Fixed by #6331
Closed

Mass selection with the shift key does not work on Incident #6283

Lhorus6 opened this issue Mar 7, 2024 · 2 comments · Fixed by #6331
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@Lhorus6
Copy link

Lhorus6 commented Mar 7, 2024

Description

On the platform, it is possible to select a set of entities by selecting a first one -> scrolling -> selecting a second one by holding down the shift key -> all entities between the first and second are selected.

However, this mechanism doesn't work with Incidents entities

Environment

OCTI 6.0.5

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Navigate to Incident
  2. In the list, select an Incident (i.e. check the box at the beginning of the line)
  3. scroll a bit
  4. Maintain shift and check the box of another report
    -> only the second incident is selected, not all in between

Expected Output

Do the repro case on Reports to understand what is expected

@Lhorus6 Lhorus6 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 7, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.6 milestone Mar 7, 2024
@jborozco jborozco removed the needs triage use to identify issue needing triage from Filigran Product team label Mar 8, 2024
@jborozco
Copy link
Member

jborozco commented Mar 8, 2024

This bug might be related to this issue #6274

@Lhorus6
Copy link
Author

Lhorus6 commented Mar 8, 2024

I don't think so. However, the issue 6274 may be linked to : #6170

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 solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
5 participants