getsentry / getsentry/sentry

[Feature Request] Configuration of the "Review list"

Open
#41,122 5 comments 0 reactions 0 assignees View on GitHub
Feature Issues > Stream/Feed
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

### Problem Statement

Sentry provides "Review list" aka "For review" functionality. It significantly simplifies an issue triage and allows to focus effort on issues that matter. However, the rules rules, by which issues are added into this list are predefined by Sentry, while in reality teams might come up with their own rules.
For example, in my team we have a weekly-rotating Sheriff, part of whose duty is to monitor Sentry, do the routing and merging, when Sentry can't do it well; notifies other teams about outstanding issues.
We have the following agreements:
- Sheriff monitors only last 2 releases;
- Sheriff needs to see **all** new issues in the monitored release, even if owner can be found automatically for such;
- We're not interested in certain issues, even if they're new/

We could've used the "Review list" but obvously the criteria for issues in it do not match what we want to see in it.

### Solution Brainstorm

- Allow configuring conditions (queries?) which define, if issues is for review;
- Allow configuring conditions (queries?), by which issues in the list can be grouped (by version for instance);
- Allow configuring actions, which remove issues from the review list.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.