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 relationship type available when creating a relationship from an Area #4092

Closed
Archidoit opened this issue Aug 17, 2023 · 2 comments · Fixed by #4094
Closed

No relationship type available when creating a relationship from an Area #4092

Archidoit opened this issue Aug 17, 2023 · 2 comments · Fixed by #4094
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)

Comments

@Archidoit
Copy link
Member

No relationship type available when creating a relationship from an Area

Steps to reproduce

Go to an Area. Go to the Knowledge tab.
Select 'Incidents' in the right tab.
Select an incident.
You can't create the relationship because there is no relationship type available.

image

It is the same from relationship from Area to other entity types (Threat actor, campaigns etc)

@Archidoit Archidoit added the bug use for describing something not working as expected label Aug 17, 2023
@RomuDeuxfois
Copy link
Member

Add a targets relationship from Incident to Area

@Archidoit
Copy link
Member Author

Note: Area will be added to Victimology.

@SamuelHassine SamuelHassine added this to the Release 5.10.0 milestone Aug 21, 2023
SamuelHassine added a commit that referenced this issue Aug 23, 2023
#4092)

Co-authored-by: Samuel Hassine <samuel.hassine@filigran.io>
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Aug 23, 2023
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

Successfully merging a pull request may close this issue.

3 participants