Skip to content

[Bug Report] Creating new performers with same name unmatches other performers #6038

@Darklyter

Description

@Darklyter

Describe the bug
When in Tagger view, if you create a new performer that has the same name as other performers (ignoring disambiguation) then it will "unmatch" the other performers from their mappings between local Stash and StashDB/TPDB. Refreshing the page or rescraping the affected scenes will show the mapped performers correctly.

To Reproduce

  1. Take an unmapped performer, for example "Trinity" and load scenes into Tagger.
  2. Match scene 1 to "Trinity (2001-2007)" (create performer if necessary)
  3. For scene 2, create a new performer named something like "Trinity (b1979, Hungary)" (creation will auto map performer)
  4. When you save that new performer, scene 1 performer will now show as unmapped with the newly created "Trinity (b1979, Hungary)" as the recommendation.
  5. Refresh page or rescrape scene 1, and "Trinity (2001-2007)" will again show as correctly mapped and matched.

Expected behavior
Would expect to not unlink other performers on new performer creation

Screenshots
You can get more explanation and a quick example video here: https://discord.com/channels/559159668438728723/559159910550732809/1399505594926370836

Stash Version: (from Settings -> About):
v0.28.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug reportBug reports that are not yet verified

    Type

    No type

    Projects

    Status

    To triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions