getsentry / getsentry/sentry

Resolve issue until defined release

Open
#43,598 10 comments 5 reactions 0 assignees View on GitHub
Feature Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

### Problem Statement

Let's say we are viewing an issue and we want to mark it as resolved. The current option, "Resolve in next release" will mark an issue as resolved but will still report it in a next patch release if it occurs again. Someone might have a different plan for whether they will actually resolve an issue in the next major or minor release. For example, when an issue occurs in release 2.0, if it is high priority, it will be fixed in release 2.1. If it is low priority, it will be fixed in release 3.0. With the current options, the issue will be marked as a regression in version 2.1 no matter the case.

### Solution Brainstorm

An additional option, "Resolve until release (...)" with options such as the precise release or "release greater than (...)" or "next major/minor release" will allow users to focus on issues with higher priority and will remind them to tackle other issues when they are able to.

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.