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

[Merge] Bad management of Author when merging several Organizations #6507

Closed
Lhorus6 opened this issue Mar 28, 2024 · 1 comment
Closed

[Merge] Bad management of Author when merging several Organizations #6507

Lhorus6 opened this issue Mar 28, 2024 · 1 comment
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

@Lhorus6
Copy link

Lhorus6 commented Mar 28, 2024

Description

When we merge more than two organizations, the Author field of the entities authored by the Organization merge (the secondary Organization), become empty instead of containing the newly merged entity.

Environment

OCTI 6.0.8

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create 3 Org -> OrgA, OrgA bis, OrgA ter
  2. Create 3 Malware -> MalA with OrgA as author, MalA bis with OrgA bis as author, etc.
  3. Go to Data > Entities and merge the 3 Org
    -> Check the field "author" of the 3 malware.

Additional information

In the lateral panel to choose the main entity (i.e. the entity for which we keep the description and the title):

  • if you keep the main organization without changing it manually -> only one of the secondary organizations is well manage in term of author (i.e. the authored entities will have the new value),
  • if you change the main organization -> no one is well manage in term of author

Screenshots

After the merge of 3 System that was the author of 3 Intrusion set

Screenshot 2024-03-28 102848

@Lhorus6 Lhorus6 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 28, 2024
@Jipegien
Copy link
Member

In the screenshot, the org proposed as default in the merge process was "SysA ter"

Other situation:
in the example, if we choose OrgA bis, the result will be

  • IntA->nothing,
  • IntA bis->OrgA bis,
  • IntA ter->nothing.

@Jipegien Jipegien removed the needs triage use to identify issue needing triage from Filigran Product team label Mar 29, 2024
@SamuelHassine SamuelHassine modified the milestones: Release 6.0.9, Release 6.0.10 Mar 30, 2024
@SamuelHassine SamuelHassine modified the milestones: Release 6.0.10, Release 6.1.0 Apr 8, 2024
@Kedae Kedae self-assigned this Apr 17, 2024
Kedae added a commit that referenced this issue Apr 17, 2024
Kedae added a commit that referenced this issue Apr 17, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Apr 17, 2024
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

4 participants