Skip to content

feat(jira): Wire Marketplace installs through the API pipeline modal#116525

Open
evanpurkhiser wants to merge 1 commit into
masterfrom
evanpurkhiser/feat-jira-wire-marketplace-installs-through-the-api-pipeline-modal
Open

feat(jira): Wire Marketplace installs through the API pipeline modal#116525
evanpurkhiser wants to merge 1 commit into
masterfrom
evanpurkhiser/feat-jira-wire-marketplace-installs-through-the-api-pipeline-modal

Conversation

@evanpurkhiser
Copy link
Copy Markdown
Member

VDY-123: Jira Cloud: API-driven integration setup

Drives the Jira Cloud Marketplace install through the API pipeline modal, the same path Discord and MS Teams use. The configure link forwards signed_params to the org-link page, which opens the pipeline modal once an organization is chosen.

The Jira step is an interactive confirmation rather than a silent auto-advance: it shows the Jira workspace (base_url) and the Sentry organization and requires the user to click "Install Jira integration" before completing. A copied install link could otherwise connect an attacker's Jira workspace to a victim's org, so the screen lets the user catch a mismatch.

  • Add the jiraIntegrationPipeline confirmation step (integrationJira/index.tsx) and register it in the pipeline registry.
  • Mark jira as an unconditional API pipeline provider.
  • Forward signed_params from the org-link page via a jiraParams memo.

Depends on the backend pipeline support in #116500 — land and deploy that first, since the modal calls the new pipeline API.

Drive the Jira Cloud Marketplace install through the API pipeline modal,
the same path Discord and MS Teams use. The configure link forwards
`signed_params` to the org-link page, which opens the pipeline modal once
an organization is chosen.

Unlike MS Teams, which auto-advances silently, the Jira step is an
interactive confirmation: it shows the Jira workspace and the Sentry
organization and requires the user to click "Install Jira integration"
before completing. A copied install link could otherwise connect an
attacker's Jira workspace to a victim's org, so the screen lets the user
catch a mismatch.

- Add the `jiraIntegrationPipeline` confirmation step and register it.
- Mark `jira` as an unconditional API pipeline provider.
- Forward `signed_params` from the org-link page via `jiraParams`.

Depends on the backend pipeline support landing first.
@evanpurkhiser evanpurkhiser requested review from a team as code owners May 29, 2026 20:30
@evanpurkhiser evanpurkhiser requested review from JoshuaKGoldberg, TkDodo, jaydgoss and leeandher and removed request for a team May 29, 2026 20:30
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label May 29, 2026
@github-actions
Copy link
Copy Markdown
Contributor

📊 Type Coverage Diff

✅ No new type safety issues introduced. Coverage: 93.59%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants