Scenario/Problem: When searching for tags in the Bitbucket repository UI, the search only matches against tokenized prefixes split by delimiters (., _, -). This means users cannot search for a meaningful portion of a tag name unless it happens to align with the start of a token boundary.

Example: A user uses a tag naming convention similar to:

• scart3.0.300

• scart2.75.300

When a user searches for 3.0.300 to find a specific release build, no results are returned because 3.0.300 does not match the start of the full tag or any individual delimeter token.

Expected behavior/Suggestion: Tag search in the Bitbucket UI should support substring matching, allowing users to type any contiguous portion of a tag name and see matching results. For example, searching 3.0.300 should return the tag scart3.0.300.

Workaround: Currently, users must type the full exact tag name or rely on a prefix that aligns with a token boundary.