Repository navigation
feat(jira): Add a Forge endpoint for the Jira configure link - #131114
Open
roggenkemper wants to merge 4 commits into
Open
roggenkemper wants to merge 4 commits into
roggenkemper wants to merge 4 commits into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The config page's caller is checked with their own Forge user token against Jira's mypermissions API, since checking another user's permissions as the app would need the app itself to be a Jira admin. Also returns 503 when Forge's signing keys can't be fetched, and matches the token helpers to the issue-events branch.
…module key What a UI invocation's module key holds isn't documented, and the admin check already decides who can link the site.
github-actions
Bot
added
Scope: Frontend
Contributor
|
🚨 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 |
roggenkemper
marked this pull request as ready for review
November 13, 2026 20:32
Christinarlong
approved these changes
Nov 13, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
POST /extensions/jira/forge/configure-link/, which the Forge config page calls to get the link that connects a Jira site to a Sentry org. It's the Forge equivalent of the link the Connect config page renders (JiraSentryInstallationView), and it reuses the same signed link and install pipeline.The endpoint:
GET /rest/api/3/mypermissions?permissions=ADMINISTER(checking another user's permissions as the app needs the app itself to be an admin);Atlassian doesn't document that its admin pages restrict who can open them, so the admin check is the guard. The page's module key isn't checked, since what a UI invocation's key holds isn't documented and the admin check already decides who can link.
Sites migrated from Connect keep using the Connect config page until they're keyed by cloud ID.