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

No error message when attempting to create an artifact without file #6052

Closed
nino-filigran opened this issue Feb 20, 2024 · 0 comments · Fixed by #6090
Closed

No error message when attempting to create an artifact without file #6052

nino-filigran opened this issue Feb 20, 2024 · 0 comments · Fixed by #6090
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

@nino-filigran
Copy link

Description

In theory, when a object is attempted to be created, there is a validation on the mandatory fields. This validation occurs, but no error message is displayed. It would be great to have an error message indicating to the user that a file must be uploaded for sake of clarity (like other entities).

Environment

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenCTI version: { e.g. OpenCTI 1.0.2 }
  3. OpenCTI client: { e.g. frontend or python }
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. go to artifact
  2. click on the + to create
  3. click on create
  4. nothing happens

Expected Output

See an error message because I did not upload a file

Actual Output

Nothing happen

Additional information

Screenshots (optional)

@nino-filigran nino-filigran added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 20, 2024
@nino-filigran nino-filigran added this to the Release 6.0.1 milestone Feb 20, 2024
@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 20, 2024
@nino-filigran nino-filigran changed the title No error message when attempting to create an atrifact without file No error message when attempting to create an artifact without file Feb 20, 2024
@CelineSebe CelineSebe self-assigned this Feb 20, 2024
CelineSebe added a commit that referenced this issue Feb 23, 2024
CelineSebe added a commit that referenced this issue Feb 23, 2024
CelineSebe added a commit that referenced this issue Feb 23, 2024
CelineSebe added a commit that referenced this issue Feb 23, 2024
CelineSebe added a commit that referenced this issue Feb 26, 2024
CelineSebe added a commit that referenced this issue Feb 26, 2024
CelineSebe added a commit that referenced this issue Feb 27, 2024
CelineSebe added a commit that referenced this issue Feb 27, 2024
…thout file (#6052)

Co-authored-by: Laurent Bonnet <146674147+labo-flg@users.noreply.github.com>
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 27, 2024
Archidoit pushed a commit that referenced this issue Jun 6, 2024
…thout file (#6052)

Co-authored-by: Laurent Bonnet <146674147+labo-flg@users.noreply.github.com>
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
3 participants