Allow arbitrary events to be assigned as "similar" instead of exclusively relying on Sentry's determination

[nwhite-riot]

Problem Statement

While I acknowledge that the "Similar Issues" feature is experimental, there are simply going to be events that Sentry can/will not identify as similar that actually are, and the current implementation of the feature leaves Sentry power users without a way to handle the similarity themselves.

Solution Brainstorm

Allow Sentry users to identify and self-assess what events are similar by adding a way to specify an event as similar in the UI.

Product Area

Issues

[linear]

ENG-5619 Allow arbitrary events to be assigned as "similar" instead of exclusively relying on Sentry's determination

[getsantry]

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

[mrduncan]

Are you familiar with merging? This sounds like what you're probably looking for

[nwhite-riot]

I am, but to my understanding, I don't have the ability to explicitly specify the events to be merged - I'm at the mercy of whatever algorithm determines similarity. Or I have to come up with a search query that captures the specific events I want and then hit the merge button. Ideally, I could copy the event ID, go to another event that I know is similar, open the "Similar Issues" section, and add the event there.

[mrduncan]

That makes sense, thanks for clarifying - yeah, the easiest way to accomplish this at the moment would be to use the issue filter on the issue stream and filter to multiple issues, for example:

We do have some plans to improve similar issues in general over the next 3-6mo, this likely is not something we will prioritize as a part of that work in the short term however