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

Add relationships and knowledge everywhere #42

Closed
SamuelHassine opened this issue May 22, 2019 · 0 comments
Closed

Add relationships and knowledge everywhere #42

SamuelHassine opened this issue May 22, 2019 · 0 comments
Assignees
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

@SamuelHassine
Copy link
Member

SamuelHassine commented May 22, 2019

Problem to Solve

Add the possibility to update the knowledge and relationships in all knowledge screens of entities/threats/techniques.

Current Workaround

Add this knowledge in report graph view.

Proposed Solution

Implement forms to add countries to region, cities to country, etc.

Additional Information

None.

@SamuelHassine SamuelHassine self-assigned this May 22, 2019
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label May 22, 2019
@SamuelHassine SamuelHassine added this to the v1.0.0 milestone May 22, 2019
@SamuelHassine SamuelHassine modified the milestones: v1.0.0, Release 1.1.0 Jun 27, 2019
@SamuelHassine SamuelHassine changed the title Update knowledge on entities views for the data catalogs Add relationships and knowledge everywhere Oct 15, 2019
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Oct 15, 2019
richard-julien pushed a commit that referenced this issue Oct 16, 2019
* [frontend/api] Implement a generic relation creation form for all knowledge screens (#42)
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