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

Organisation type vs category #427

Closed
Fred-certeu opened this issue Jan 20, 2020 · 0 comments
Closed

Organisation type vs category #427

Fred-certeu opened this issue Jan 20, 2020 · 0 comments
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

@Fred-certeu
Copy link

Please replace every line in curly brackets { like this } with an appropriate answer, and remove this line.

Description

Organisation "type" or "partner" are used to designate the same thing apparently
"type" is the term visible in the view mode
"category" is the term visible in the edit mode

This should be made consistent

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. { e.g. Run ... }
  2. { e.g. Click ... }
  3. { e.g. Error ... }

Expected Output

{ Please describe what you expected to happen. }

Actual Output

{ Please describe what actually happened. }

Additional information

{ Any additional information, including logs or screenshots if you have any. }

@SamuelHassine SamuelHassine self-assigned this Jan 20, 2020
@SamuelHassine SamuelHassine added the bug use for describing something not working as expected label Jan 20, 2020
@SamuelHassine SamuelHassine added this to the Release 2.1.3 milestone Jan 20, 2020
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 22, 2020
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

No branches or pull requests

2 participants