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

When upserting an entity, name should also change #6315

Closed
2 tasks
SamuelHassine opened this issue Mar 12, 2024 · 1 comment
Closed
2 tasks

When upserting an entity, name should also change #6315

SamuelHassine opened this issue Mar 12, 2024 · 1 comment
Assignees
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@SamuelHassine
Copy link
Member

SamuelHassine commented Mar 12, 2024

Description

  1. Create an entity named "A" confidence = 75
  2. Add alias "B" to entity A
  3. Try to create the entity named "B" confidence = 75

Current result: Nothing
Expected result: Entity A is now named B and A is put in alias of B

This was the previous behavior and it is critical for data health.

  • Bug fixed
  • Integration test coded
@SamuelHassine SamuelHassine added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team critical use to identify critical bug to fix ASAP and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 12, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.6 milestone Mar 12, 2024
@jpkha jpkha self-assigned this Mar 12, 2024
@jpkha
Copy link
Member

jpkha commented Mar 12, 2024

@SamuelHassine SamuelHassine assigned SamuelHassine and unassigned jpkha Mar 12, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 12, 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 critical use to identify critical bug to fix ASAP 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

2 participants