getsentry / getsentry/sentry

Publish public documentation for issue linking API

Open
#85,565 7 comments 1 reaction 0 assignees View on GitHub
Feature Product Area: Settings - Integrations
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

[Reported via Discord](https://discord.com/channels/621778831602221064/1341800780784599050/1341800780784599050): For now, the only ways to create a Jira issue when a sentry event happens is the Alert system or have an user do manually via the GUI.

Would it be possible to do it with an API endpoint ? Basically, the whole Sentry/Jira integration i(and the release system) is too "light" for us, and we want to have our own service running to synchronise things. But we can't link a Sentry issue with a jira ticket via API.

### Solution Brainstorm

_No response_

### Product Area

Settings - Integrations

Contributor guide

Open the contributing guide

Research direction

Start in Settings - Integrations by reviewing the existing Sentry/Jira integration and any current issue-linking API surface. The issue names no files, tests, or entry points, so first clarify whether the work is to add an API endpoint, publish documentation for an existing endpoint, or both; completion criteria are not defined.

Written by the indexing model from the issue text.

Assessment

Domain
api, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.