feat(issues): Add endpoint for pull requests linked to an issue by scttcper · Pull Request #116744 · getsentry/sentry

scttcper · 2026-06-02T23:38:33Z

Linked PRs only live in the activity timeline today This adds a current-state read API so the recent ones can be surfaced somewhere more useful like the issue sidebar.

GET /organizations/{org}/issues/{issue_id}/pull-requests/ returns the 5 most recent PRs linked through GroupLink, with a best-effort status that's live-fetched for GitHub/GHE and unknown everywhere else.

gated behind organizations:issue-details-linked-pull-requests.

part of CORE-207

Linked PRs only lived in the activity timeline, which is historical and capped. This adds a current-state read API that pulls the high-signal recent PRs out of activity and into something the sidebar can render. GET /organizations/{org}/issues/{issue_id}/pull-requests/ returns the 5 most recent PRs linked through GroupLink (pull_request + resolves) in the last 90 days, newest first. Reuses PullRequestSerializer for the base fields and decorates each row with dateLinked and a best-effort status (merged/open/closed/draft/unknown). Status is live-fetched via the integration client for GitHub/GHE only, scoped to the PR org so a stale Repository.integration_id can't reach another org's installation. Anything else degrades to unknown. Nothing is persisted, status from webhooks can be a follow-up. Gated behind organizations:issue-details-linked-pull-requests, backend only for now. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

github-actions · 2026-06-02T23:40:46Z

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

mypy flagged the create_linked_pull_request helper for missing param and return types. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Add the new group pull requests URL name to the region-pinned list so getsentry URL action checks know how to route it. Co-Authored-By: Codex GPT-5 <noreply@openai.com>

Push the org filter into the pull request lookup instead of filtering the bulk result in Python. Keeps the GroupLink ordering, just makes the access boundary more obvious. Co-Authored-By: Codex GPT-5 <noreply@openai.com>

Normalize the tiny provider response shape before mapping it to the sidebar PR status. Keeps the fallback behavior the same, just makes the status code a little easier to read and type. Co-Authored-By: Codex GPT-5 <noreply@openai.com>

Use explicit literal returns for provider PR states so full backend typing can verify the PullRequestStatus response type. Co-Authored-By: Codex GPT-5 <noreply@openai.com>

Keep the linked pull requests endpoint off the legacy unscoped group URL helper so getsentry URL validation does not need a new deprecated action entry. Regenerate known API URL types after removing the legacy issues/groups pull-requests routes. Co-Authored-By: Codex GPT-5 <noreply@openai.com>

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 4a349c2. Configure here.}

Remove the deprecation decorator from the new endpoint and stop filtering linked pull requests by age. The response remains capped to the five newest resolving links. Co-Authored-By: Codex GPT-5 <noreply@openai.com>

linear-code · 2026-06-03T23:23:37Z

CORE-207

# Conflicts: # static/app/utils/api/knownSentryApiUrls.generated.ts

shashjar · 2026-06-08T17:03:50Z

+
+        assert response.status_code == 404
+
+    def test_empty_response(self) -> None:


Could add a test that limit of 5 PRs is respected when there are more than 5 that exist

Maybe also when a PR or repo gets deleted?

shashjar · 2026-06-08T17:05:28Z

+            title="Commit link",
+            linked_type=GroupLink.LinkedType.commit,
+        )
+        Activity.objects.create(


it's silly but i think the SET_RESOLVED_IN_PULL_REQUEST Activity is actually irrelevant to issue resolution via PR behavior (although probably still good to include in the test for consistency). more discussion of that here: https://sentry.slack.com/archives/C0B349R63M1/p1779886618643259

shashjar · 2026-06-08T17:06:52Z

+        }
+        date_linked_by_pr_id = {link.linked_id: link.datetime for link in group_links}
+        pull_request_responses: list[LinkedPullRequestResponse] = []
+        for pull_request in pull_requests:


probably doesn't matter in practice but could maybe issue these status requests in parallel if latency becomes a factor

shayna-ch · 2026-06-08T17:07:45Z

+                project_id=group.project_id,
+                linked_type=GroupLink.LinkedType.pull_request,
+                relationship=GroupLink.Relationship.resolves,
+            ).order_by("-datetime")[:DEFAULT_LIMIT]


Should the 90 day time frame be specified here?

i ended up removing the 90 day time frame, i can clean that up more

cvxluo · 2026-06-08T17:02:01Z

+
+    installation = integration.get_installation(organization_id=pull_request.organization_id)
+    client = installation.get_client()
+    get_pull_request = getattr(client, "get_pull_request", None)


should we be using the SCM platform to retrieve PRs?

maybe soon?

github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Jun 2, 2026

🛠️ Sync API Urls to TypeScript

aef97cf

github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jun 2, 2026

vercel Bot deployed to Preview June 2, 2026 23:42 View deployment

scttcper and others added 6 commits June 2, 2026 17:08

test(issues): Annotate linked PR test helper

137cf6b

mypy flagged the create_linked_pull_request helper for missing param and return types. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

fix(issues): Pin linked pull requests endpoint

0154fff

Add the new group pull requests URL name to the region-pinned list so getsentry URL action checks know how to route it. Co-Authored-By: Codex GPT-5 <noreply@openai.com>

fix(issues): Scope linked pull request query

1c0abf9

Push the org filter into the pull request lookup instead of filtering the bulk result in Python. Keeps the GroupLink ordering, just makes the access boundary more obvious. Co-Authored-By: Codex GPT-5 <noreply@openai.com>

ref(issues): Type linked pull request status

8a31af6

Normalize the tiny provider response shape before mapping it to the sidebar PR status. Keeps the fallback behavior the same, just makes the status code a little easier to read and type. Co-Authored-By: Codex GPT-5 <noreply@openai.com>

fix(issues): Narrow linked pull request status

6c4910f

Use explicit literal returns for provider PR states so full backend typing can verify the PullRequestStatus response type. Co-Authored-By: Codex GPT-5 <noreply@openai.com>

vercel Bot deployed to Preview June 3, 2026 23:01 View deployment

scttcper marked this pull request as ready for review June 3, 2026 23:02

scttcper requested review from a team as code owners June 3, 2026 23:02

cursor Bot reviewed Jun 3, 2026

View reviewed changes

Comment thread src/sentry/issues/endpoints/group_pull_requests.py

sentry Bot reviewed Jun 3, 2026

View reviewed changes

Comment thread src/sentry/issues/endpoints/group_pull_requests.py Outdated

fix(issues): Keep linked pull requests endpoint active

969149d

Remove the deprecation decorator from the new endpoint and stop filtering linked pull requests by age. The response remains capped to the five newest resolving links. Co-Authored-By: Codex GPT-5 <noreply@openai.com>

Merge branch 'master' into scttcper/issue-linked-pull-requests

a75e3bc

vercel Bot deployed to Preview June 4, 2026 17:13 View deployment

Merge branch 'master' into scttcper/issue-linked-pull-requests

895a379

vercel Bot deployed to Preview June 4, 2026 17:30 View deployment

Merge branch 'master' into scttcper/issue-linked-pull-requests

d7b47dc

# Conflicts: # static/app/utils/api/knownSentryApiUrls.generated.ts

vercel Bot deployed to Preview June 8, 2026 16:29 View deployment

shashjar approved these changes Jun 8, 2026

View reviewed changes

shayna-ch reviewed Jun 8, 2026

View reviewed changes

cvxluo approved these changes Jun 8, 2026

View reviewed changes

scttcper added 3 commits June 8, 2026 13:52

fix(issues): Filter invalid linked pull requests

8ee202f

Merge branch 'master' into scttcper/issue-linked-pull-requests

6df4f95

test(issues): Set disabled repository status in linked PR test

c6263ba

scttcper enabled auto-merge (squash) June 8, 2026 23:08

scttcper merged commit 02ffc5e into master Jun 8, 2026
117 of 119 checks passed

scttcper deleted the scttcper/issue-linked-pull-requests branch June 8, 2026 23:11

sentry-release-bot Bot mentioned this pull request Jun 15, 2026

publish: getsentry/sentry@26.6.0 getsentry/publish#8571

Closed

3 tasks


		assert response.status_code == 404

		def test_empty_response(self) -> None:

Uh oh!

Uh oh!

Conversation

scttcper commented Jun 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Jun 2, 2026

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

linear-code Bot commented Jun 3, 2026

Uh oh!

shashjar Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

shashjar Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

shashjar Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

shashjar Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

shayna-ch Jun 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

scttcper Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

cvxluo Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

scttcper Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

scttcper commented Jun 2, 2026 •

edited

Loading

shayna-ch Jun 8, 2026 •

edited

Loading