Feature Request: Add StashIDs Manually in UI for all Objects

[Gykes]

Describe the feature you'd like

With the addition of StashID support for tags it looks like it may be time to finally add the ability to manually add or search for StashIDs to the various objects that support them (Scenes, Performers, Studios, Tags).

Describe the benefits this would bring to existing users

Better matching?

Is there an existing way to achieve this goal?

Via plugins but you have to manually find the ID on your respective Stashbox and add it manually.

Have you searched for an existing open/closed issue?

• I have searched for existing issues and none cover the core request of my proposal

Additional context

From WithoutPants:
"I figure an add button dropdown to select the stash-box instance, then opens a dialog to search for the object via name or stash id"

I pretty much agree with that implantation. Something much simpler like how the current StashID Input plugin works would be good as well for just straight up manual entry but it's already a plugin so might not want to spend the time moving that to core.

[Gykes]

So my thought on this are as such:

1. User clicks Add/IDs or some variation button with a dropdown showing available stash-box instances
2. Selects which stash-box instance to search
3. Opens a search dialog where they can search by:
   - Name (e.g., "Brazzers" for a studio)
   - Stash ID (direct lookup)
4. Shows search results from that stash-box
5. User selects the correct match
6. Adds that stash ID to the local object

I feel like this would essentially just be tagger but one Studio/Scene/Performer/Tag at a time.

If we dont want to get that complex we can essentially move this plugin to core. https://docs.stashapp.cc/plugins/list/#stash-stashid-input

This would allow users to add tags manually but it would not give them the search option.

[WithoutPants]

I'd prefer not to allow users to easily add potentially invalid stash-ids in the core UI. Using a search modal is a little more complex, but I think it's the nicer way to go.

Implementation considerations:

• reuse the search modal components as much as possible

[Gykes]

Understood, i'll look into implementing it.