Skip to content

chore(jira): Add Forge app manifest for Connect-to-Forge migration#115603

Draft
BYK wants to merge 1 commit into
masterfrom
BYK/chore/add-jira-forge-manifest
Draft

chore(jira): Add Forge app manifest for Connect-to-Forge migration#115603
BYK wants to merge 1 commit into
masterfrom
BYK/chore/add-jira-forge-manifest

Conversation

@BYK
Copy link
Copy Markdown
Member

@BYK BYK commented May 14, 2026

Add the Atlassian Forge manifest.yml for the Jira Cloud integration, co-located with the existing integration code at src/sentry/integrations/jira/forge/.

Atlassian is sunsetting Connect apps and requiring migration to Forge. This manifest wraps the existing Connect app ("Sentry for Jira", key sentry.io.jira) as a Forge remote app, proxying all requests back to sentry.io. It has already been deployed to production and linked to the existing Marketplace listing as a private version (v2.0.0) pending validation before public rollout.

The manifest defines:

  • Lifecycle hooks (install/uninstall)
  • Configuration and post-install pages
  • Jira issue context panel (linked issues glance)
  • Webhook for issue updates
  • Connect-compatible scopes

Add the Atlassian Forge manifest.yml for the Jira Cloud integration. This is the configuration file used to publish the Forge version of the existing "Sentry for Jira" Connect app on the Atlassian Marketplace, as part of the Connect-to-Forge migration required by Atlassian's Connect end-of-support plan.
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant