-
Notifications
You must be signed in to change notification settings - Fork 799
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
Issue/2559 Display all indicators/observables contained in reports which contain a specific entity(#2559) #3764
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SamuelHassine
force-pushed
the
master
branch
2 times, most recently
from
July 21, 2023 09:21
725e4e4
to
4cca592
Compare
RomuDeuxfois
force-pushed
the
issue/2559
branch
3 times, most recently
from
July 25, 2023 12:45
3d97215
to
daea399
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...cti-platform/opencti-graphql/src/modules/threatActorIndividual/threatActorIndividual.graphql
Outdated
Show resolved
Hide resolved
PR status
1 new issue to be fixed:
|
marieflorescontact
force-pushed
the
issue/2559
branch
from
July 28, 2023 13:33
74778c1
to
1fbac52
Compare
PR status
PR ready for review |
@@ -85,7 +85,6 @@ type ThreatActorIndividual implements BasicObject & StixObject & StixCoreObject | |||
filters: [StixCoreRelationshipsFiltering] | |||
filterMode: FilterMode | |||
): [Distribution] @auth(for: [KNOWLEDGE, EXPLORE]) | |||
# StixDomainObject |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you put back this comment, please?
RomuDeuxfois
force-pushed
the
issue/2559
branch
from
August 1, 2023 09:18
1fbac52
to
5908f40
Compare
PR status
PR ready for review 🔥 🔥 🔥 |
yassine-ouaamou
approved these changes
Aug 1, 2023
Archidoit
approved these changes
Aug 1, 2023
…psStixCyberObservable component and fix StixCoreRelationshipCreationFromEntity
RomuDeuxfois
force-pushed
the
issue/2559
branch
from
August 2, 2023 09:53
5908f40
to
0cece93
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the 1st part of the issue applied to the
Threat Actor Individual
, once approved we will extend it to the rest of the entities concerned.Related Brainstorm
Explanation of code structure and opening on the next step
Proposed changes
Indicators
tab from the knowledge TopbarIndicators
are now accesible from the knowledge right bar aboveObservables
contextual view
that displaysObservables/Indicators
that are contained inReports/Case/Grouping
that contains the Entityview component
to displayEntistixCorerelationships
:EntitiesView
/RelationshipView
/ContextualView
Pattern Type
andIndicator type
for Indicators entities viewRelated issues
Checklist
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...