Explicit tag syntax not working in new issue view

[kerenkhatiwada]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Originally reported via Discord here.

Searching using the explicit tag syntax (tags[platform]:tag_value) works as expected in the old issue view but is broken in the new issue view.

In the new issue view, after entering tags[platform]:tag_value in the search bar and hitting Enter, nothing happens. This was tested on this issue.

Repro Video:

Screen.Recording.2025-04-03.at.9.04.53.AM.mov

Expected Result

Explicit Tag Syntax search works on the new issue view and returns correct events

Actual Result

Explicit Tag Syntax search doesn't work on the new issue view

Product Area

Issues

Link

No response

DSN

No response

Version

No response

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[scttcper]

These features are all powered by discover so any query that works in discover will work here. For tags like platform you should be able to use platform:xyz

[TheCrossBoy]

These features are all powered by discover so any query that works in discover will work here. For tags like platform you should be able to use platform:xyz

If I use platform:xyz, the options are populated inside it, and in the search results, many results come up but they are all listed as having 0 issues for some reason:

if I use tags[platform]:xyz, the issues do show up, but annoyingly, if I click on one of them, it doesn't pick an event that has that tag matching, it just picks whatever event in it it wants, which is confusing. Though that may be a separate ticket.

The tags syntax is fine, but annoyingly, it is formatted the exact same way after hitting :, and it presents the exact same options:

I will say, the use case I was trying to do was to overwrite the Platform variable, but I didn't see a "correct" way of doing this, so I was just using tags instead. However, I've now found that I can actually update the variable by using the Unity SDK's AddEventProcessor. So moving forward I'll do it that way, though it's a shame the existing errors won't be grouped correctly.

[roggenkemper]

@TheCrossBoy I looked into this a bit more and think I found what's wrong. this bug should be fixed in #88745