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

The field DESCRIPTION of a vulnerability is not displayed. #1015

Closed
csandu-certeu opened this issue Jan 21, 2021 · 0 comments
Closed

The field DESCRIPTION of a vulnerability is not displayed. #1015

csandu-certeu opened this issue Jan 21, 2021 · 0 comments
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@csandu-certeu
Copy link

Description

The field DESCRIPTION is not shown. You can edit the description field, it but it is not displayed.

Environment

  1. OS (where OpenCTI server runs): Mac OS
  2. OpenCTI version: OpenCTI
  3. OpenCTI client: frontend
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Open a vulnerability
  2. On the KNOWLEDGE tab the user should see the description of the vulnerability.
  3. That is not the case, but the user can, however, edit the description if he starts editing the vulnerability.

Expected Output

The description of the vulnerability should be displayed in the section DETAILS, next to the LABELS.

Actual Output

Desription is not displayed.

Additional information

@SamuelHassine SamuelHassine added this to the Release 4.1.0 milestone Jan 25, 2021
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Jan 25, 2021
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants