getsentry / getsentry/sentry

Possibility to change default "Resolve" action by project

Open
#75,320 7 comments 4 reactions 0 assignees View on GitHub
Feature Integrations Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

We are currently using the Azure Devops integration and our workflow for some projects are that once an issue has been fixed it is committed to our master and release branches.
A new version is published from these branches daily at a fixed schedule.

Our developers complete their Tasks once their pull requests have gone through but before the version has been released.
The Azure Devops integration however marks the Issues as "Resolved" as soon as the Azure Devops bug is completed.

The solution:
If it was possible to change the default "Resolve" action for a project to - "Fixed in next version" this would solve this issue in our workflow.

Currently the developers needs to manually Resolve the issue and select the correct version once that version is released which is very time consuming.

### Solution Brainstorm

_No response_

### Product Area

Releases

Contributor guide

Open the contributing guide

Research direction

Start by tracing the Azure DevOps integration's handling of completed bugs and the project-level release settings. Define how a project's default Resolve action should be selected, then verify that the existing workflow still resolves issues with the requested version behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, python
Domain
release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.