getsentry / getsentry/sentry

[Jira Integration] Add option to unlink upon Sentry issue when resolving linked Jira issue

Open
#91,802 2 comments 3 reactions 0 assignees View on GitHub
Product Area: Settings - Integrations
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

Creating this from feedback from a user in this Zendesk ticket: https://sentry.zendesk.com/agent/tickets/152765

I notice this also came up here in this closed Issue: https://github.com/getsentry/sentry/issues/79073

When a linked issue in Sentry regresses, it reopens the linked Jira ticket as well. Some users would like for a new Jira ticket to be created instead of the same one reopening constantly. At the same time, users would also like to keep the context of the old linked Sentry issue.

If on resolving the linked Jira issue also unlinks the Sentry issue after resolve, it frees up the Sentry issue to create a new Jira issue when the alert is triggered again.

### Solution Brainstorm

Add an option to the integration Configuration to also send a request to unlink on resolve

### Product Area

Settings - Integrations

Contributor guide

Open the contributing guide

Research direction

Start by tracing the Jira integration Configuration and the resolve flow for linked Sentry issues. Review how regressions currently reopen Jira tickets and how unlink requests are handled. Done should include a configurable resolve-time unlink that lets a later alert create a new Jira ticket while preserving the old Sentry issue context.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.