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.

Sign up for GitHub

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

Jump to bottom

Inferred relation instrusion set - country - region #220

Closed
michaelheider opened this issue Sep 17, 2019 · 1 comment
Closed

Inferred relation instrusion set - country - region #220

michaelheider opened this issue Sep 17, 2019 · 1 comment
Assignees
@SamuelHassine
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
Release 2.0.0

Comments

@michaelheider
Copy link

Problem to Solve

When an intrusion set attacks a country that is located in a region, then there is an inferred relation that states that the intrusion set also attacks the region.
However, when the intrusion set is set to attack the region, which has a country located in it, then there is no inferred relation that states that the intrusion set also attacks the country.
This causes attacking intrusion sets not to be displayed when viewing an individual country, even though intrusion sets that are targeting a region that includes the country clearly are also targeting the single country.

Current Workaround

None.

Proposed Solution

Implement inferred relation also the other way round, as described above.

Additional Information

None.
@richard-julien richard-julien added the feature use for describing a new feature to develop label Sep 17, 2019
@SamuelHassine SamuelHassine added bug use for describing something not working as expected and removed feature use for describing a new feature to develop labels Oct 14, 2019
@SamuelHassine SamuelHassine self-assigned this Oct 14, 2019
@SamuelHassine SamuelHassine added this to the Release 2.0.0 milestone Oct 14, 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
@SamuelHassine
Copy link
Member

Will be fixed in 2.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SamuelHassine SamuelHassine

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
Milestone
Release 2.0.0
Development

No branches or pull requests
3 participants
@richard-julien @SamuelHassine @michaelheider