getsentry / getsentry/sentry

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

Open
#100,414 5 comments 0 reactions 0 assignees View on GitHub
Feature Product Area: Issues
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### 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

Contributor guide

Open the contributing guide

Research direction

The issue concerns the experimental Similar Issues feature in Sentry's Issues product area, but it names no files, tests, or entry points. Start by locating the Similar Issues UI and its current similarity-assignment flow; done would mean users can specify an event as similar themselves.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.