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

I can't create indicators within a report at once. #6274

Closed
misohouse opened this issue Mar 4, 2024 · 1 comment · Fixed by #6306
Closed

I can't create indicators within a report at once. #6274

misohouse opened this issue Mar 4, 2024 · 1 comment · Fixed by #6306
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

@misohouse
Copy link

OpenCTI version: 6.0.4

Clicking on each object individually activates the button to create an indicator,
11

If I hold down the "Shift" button and select the objects at once, the button to create an indicator is not activated.
22

It is too inconvenient to select many observable objects one by one.

I think it's a bug, but please confirm.

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

Lhorus6 commented Mar 8, 2024

May be linked to : #6170

@Archidoit Archidoit self-assigned this Mar 11, 2024
@Archidoit Archidoit linked a pull request Mar 11, 2024 that will close this issue
@Archidoit Archidoit added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 12, 2024
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
Development

Successfully merging a pull request may close this issue.

5 participants