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

Finding report duplicates does not work properly #8800

Closed
ups1decyber opened this issue Oct 28, 2024 · 2 comments
Closed

Finding report duplicates does not work properly #8800

ups1decyber opened this issue Oct 28, 2024 · 2 comments
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) ui for scope limited to UI change
Milestone

Comments

@ups1decyber
Copy link

Description

We noticed that analysts sometimes produced duplicate reports in OpenCTI for OSINT reports. After some testing, we noticed that the detection of potential duplicates is not triggered when a report title is pasted into the text field.

Environment

  1. OpenCTI version: 6.3.1

Reproducible Steps

  1. Create a report with name Reporty McReportface (or something else :) )
  2. Copy the report title
  3. Open the dialog to create another report and paste the title
  4. You should now see a hint that a potential duplicate was found, but instead, it is shown that there is no potential duplicate

Expected Output

You should now see a hint that a potential duplicate was found, but instead ...

Actual Output

... it is shown that there is no potential duplicate.

Additional information

none

Screenshots (optional)

@ups1decyber ups1decyber added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Oct 28, 2024
@romain-filigran
Copy link
Member

Hi @ups1decyber :The duplication notification is correctly displayed if you manually enter the report name but in fact it is not triggered when you copy/paste the name. We'll see if we can improve this behavior

@romain-filigran romain-filigran added ui for scope limited to UI change and removed needs triage use to identify issue needing triage from Filigran Product team labels Oct 28, 2024
@romain-filigran romain-filigran added this to the Bugs backlog milestone Oct 28, 2024
@CelineSebe
Copy link
Member

Already fix with #8180 I think

@CelineSebe CelineSebe self-assigned this Oct 31, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Oct 31, 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) ui for scope limited to UI change
Projects
None yet
Development

No branches or pull requests

4 participants