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.

Sign up for GitHub

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

Jump to bottom

Bug/Regression - Bulk edition of status not possible #8393

Closed
Lhorus6 opened this issue Sep 17, 2024 · 1 comment · Fixed by #8400
Closed

Bug/Regression - Bulk edition of status not possible #8393

Lhorus6 opened this issue Sep 17, 2024 · 1 comment · Fixed by #8400
Assignees
@Archidoit
Labels
bug use for describing something not working as expected regression Label to identify the bug as a regression of previously working feature solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 6.3.3

Comments

@Lhorus6
Copy link

Lhorus6 commented Sep 17, 2024

Description

I'd like to change Vulnerability status en masse but I can't do it anymore (i.e. Select several Vulns > Update > Replace > ‘status’ option not available). I am not sure if we could do it in the past on Vulnerability, I imagine we could. One thing's for sure: we were able to at least do it on Reports, but that's no longer possible.

Environment

OCTI 6.3.0

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Select several Report and click on "update"

Screenshot 2024-09-18 003814

  1. "Replace" then open the drop down menu

image

We no longer have "status"
@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 Sep 17, 2024
@nino-filigran
Copy link

Ok to be clear the fix should be to be able to update the status on all entities having mass operations.

@nino-filigran nino-filigran added regression Label to identify the bug as a regression of previously working feature and removed needs triage use to identify issue needing triage from Filigran Product team labels Sep 18, 2024
@nino-filigran nino-filigran added this to the Bugs backlog milestone Sep 18, 2024
@Archidoit Archidoit self-assigned this Sep 18, 2024
@Archidoit Archidoit modified the milestones: Bugs backlog, Release 6.4.0 Sep 18, 2024
Archidoit added a commit that referenced this issue Sep 18, 2024
@Archidoit
[frontend] Bulk edition of status regression fix (#8393)
f36a7b8
@Archidoit Archidoit mentioned this issue Sep 18, 2024
Merged
@Archidoit Archidoit linked a pull request Sep 18, 2024 that will close this issue
[frontend] Bulk edition of status regression fix (#8393) #8400
Merged
@labo-flg labo-flg modified the milestones: Release 6.4.0, Release 6.3.2 Sep 18, 2024
Archidoit added a commit that referenced this issue Sep 19, 2024
@Archidoit
[frontend] Bulk edition of status regression fix (#8393)
cc372ee
Archidoit added a commit that referenced this issue Sep 19, 2024
@Archidoit
[frontend] Bulk edition of status regression fix (#8393)
8d24ac1
Archidoit added a commit that referenced this issue Sep 19, 2024
@Archidoit
[frontend] Bulk edition of status regression fix (#8393)
c0cddce
@Kedae Kedae modified the milestones: Release 6.3.2, Release 6.3.3 Sep 19, 2024
Archidoit added a commit that referenced this issue Sep 20, 2024
@Archidoit
[frontend] Bulk edition of status regression fix (#8393)
1f099b8
@Archidoit Archidoit added the solved use to identify issue that has been solved (must be linked to the solving PR) label Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Archidoit Archidoit

Labels
bug use for describing something not working as expected regression Label to identify the bug as a regression of previously working feature solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 6.3.3
Development

Successfully merging a pull request may close this issue.

[frontend] Bulk edition of status regression fix (#8393) OpenCTI-Platform/opencti
6 participants
@SamuelHassine @Kedae @Lhorus6 @Archidoit @labo-flg @nino-filigran