Submit to StashDB -> Tag Mapping Defaults are Non Explicit

Describe the bug

Submission of a scene with an all male cast (link) with tags scraped directly from source included a tag Trimmed which was auto mapped into a tag during submission called Trimmed Pussy

Tag mapping should be explicit. Eg. if the tag “Trimmed” does not exist it shouldn’t automatically map to one called “Trimmed Pussy”. Likely a non explicit check occurring.

Steps to reproduce

Submit a video with the tag “Trimmed” and check for the automatic map to “Trimmed Pussy”

Expected behaviour

“Trimmed” if explicit match for tag does not exist in StashDB should appear in the “Tags not mapped” area above the post to be manually added by user

Screenshots or additional context

Stash/stash-box version

LTS / Docker

v0.30.1

Build hash:

b23b0267

Build time:

2025-12-18 04:50:05

Device details

Browser: Brave (Chrome)

Relevant log output

N/a

Not a bug.

StashDB instance has Trimmed as an alias of Trimmed Pussy tag.

You can discuss a change in StashDB > Ministry of Truth.

Alternatively, you can bypass name matching entirely when submitting via draft from Stash, by adding Stash ID. When tag has Stash ID, it gets matched directly based on that ID and not the name.

E.g. If your local Trimmed tag had Stash ID = d35af0a1-2895-4924-8609-974992b73312 for StashDB, it would always use Trimmed Dick when you are submitting drafts.

1 Like