Add issue identification to 'link issue' form field component uri request
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Problem Statement
I have a custom integration build where I create and link issues to my own ticketing platform. When I want to connect an issue or create one, I want ro be able to only select the project(s) that is relevant for that specific Sentry issue but I can't identify wich issue is triggering the request to my webserver getting projects and other info so I must return all projects available despite of permissions on my plstform to see them or not. This is possible when using webhooks but I want manually creating tickets from the Sentry issue detail interface. I believe this is basic functionality.
### Solution Brainstorm
Add an issue short key or other ID to identify the issue where the create of link issue button is triggered.
### Product Area
Issues
Contributor guide
Research direction
Start with the 'link issue' form field component URI request described in the issue and inspect how the Sentry issue detail interface requests projects and related data. Determine how the triggering issue can be identified by the integration, then verify that the request exposes an issue short key or equivalent ID and that project selection remains scoped to that issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100