Self-Hosted Version
26.5.1
CPU Architecture
aarch64
Docker Version
25.0.14
Docker Compose Version
5.4.0
Machine Specification
Installation Type
Fresh install
Steps to Reproduce
Summary
I'm trying to integrate a self-hosted Sentry (v26.5.1) instance with Jira Cloud to allow developers to create Jira issues directly from Sentry.
After investigating with both Atlassian and Sentry Support, it appears that the documented installation method is no longer supported due to recent Atlassian platform changes.
I'm opening this issue to understand whether there is now a supported installation method for new self-hosted deployments or whether this is a known limitation.
Environment
Sentry Version: 26.5.1
Deployment: Self-hosted
Jira: Jira Cloud
Sentry URL: (https://sentry.int.xxxx.cloud)
Goal
Configure the standard Jira Cloud integration for a self-hosted Sentry instance so that developers can:
Create Jira issues directly from Sentry
Link Sentry issues with Jira issues
View Jira issue status from Sentry
What I have verified
The environment has been thoroughly validated.
- Sentry is publicly accessible.
- Valid public SSL certificate.
- Public FQDN.
- No VPN restrictions.
- The Sentry server can communicate with Jira Cloud.
- The Jira Connect descriptor is available and returns successfully.
Descriptor URL:
https://sentry.int.xxxx.cloud/extensions/jira/descriptor/
Expected Result
I expected to be able to configure the standard Jira Cloud integration for a self-hosted Sentry instance by following the official documentation.
Specifically, I expected to:
Install the Jira integration using the documented self-hosted installation flow.
Connect my self-hosted Sentry instance to Jira Cloud.
Create Jira issues directly from Sentry.
Link Sentry issues with Jira issues.
View Jira issue status from within Sentry.
Since my environment satisfies the documented prerequisites (public FQDN, valid SSL certificate, publicly accessible instance, reachable descriptor URL, and connectivity between Sentry and Jira Cloud), I expected the integration to install successfully.
Actual Result
The environment has been thoroughly validated.
- Sentry is publicly accessible.
- Valid public SSL certificate.
- Public FQDN.
- No VPN restrictions.
- The Sentry server can communicate with Jira Cloud.
- The Jira Connect descriptor is available and returns successfully.
Descriptor URL:
https://sentry.int.xxxx.cloud/extensions/jira/descriptor/
However, I cannot install the Jira integration.
The official Sentry for Jira Marketplace app redirects authentication to sentry.io, which only supports Sentry SaaS organizations.
The documented self-hosted installation method relies on installing the local Atlassian Connect descriptor.
However, Jira Cloud no longer supports installing new private Atlassian Connect applications using descriptor URLs on production sites, preventing the documented installation flow from completing.
To verify this was not an environment issue, I contacted both Atlassian Support and Sentry Support.
Atlassian confirmed that:
New private Atlassian Connect applications can no longer be installed via descriptor URLs on Jira Cloud production sites.
Development Mode no longer allows descriptor-based installations.
The recommended installation methods are Marketplace apps or Forge.
Sentry Support confirmed that:
The documented installation method for self-hosted Sentry is still the Connect descriptor (/extensions/jira/descriptor/).
The Marketplace app is intended only for Sentry SaaS (sentry.io).
Atlassian's retirement of descriptor-based installations blocks the documented installation flow.
There is currently no documented replacement installation mechanism for self-hosted Sentry.
As a result, I was unable to complete the integration despite meeting all documented prerequisites.
Event ID
No response
Self-Hosted Version
26.5.1
CPU Architecture
aarch64
Docker Version
25.0.14
Docker Compose Version
5.4.0
Machine Specification
Installation Type
Fresh install
Steps to Reproduce
Summary
I'm trying to integrate a self-hosted Sentry (v26.5.1) instance with Jira Cloud to allow developers to create Jira issues directly from Sentry.
After investigating with both Atlassian and Sentry Support, it appears that the documented installation method is no longer supported due to recent Atlassian platform changes.
I'm opening this issue to understand whether there is now a supported installation method for new self-hosted deployments or whether this is a known limitation.
Environment
Sentry Version: 26.5.1
Deployment: Self-hosted
Jira: Jira Cloud
Sentry URL: (https://sentry.int.xxxx.cloud)
Goal
Configure the standard Jira Cloud integration for a self-hosted Sentry instance so that developers can:
Create Jira issues directly from Sentry
Link Sentry issues with Jira issues
View Jira issue status from Sentry
What I have verified
The environment has been thoroughly validated.
Descriptor URL:
https://sentry.int.xxxx.cloud/extensions/jira/descriptor/
Expected Result
I expected to be able to configure the standard Jira Cloud integration for a self-hosted Sentry instance by following the official documentation.
Specifically, I expected to:
Install the Jira integration using the documented self-hosted installation flow.
Connect my self-hosted Sentry instance to Jira Cloud.
Create Jira issues directly from Sentry.
Link Sentry issues with Jira issues.
View Jira issue status from within Sentry.
Since my environment satisfies the documented prerequisites (public FQDN, valid SSL certificate, publicly accessible instance, reachable descriptor URL, and connectivity between Sentry and Jira Cloud), I expected the integration to install successfully.
Actual Result
The environment has been thoroughly validated.
Descriptor URL:
https://sentry.int.xxxx.cloud/extensions/jira/descriptor/
However, I cannot install the Jira integration.
The official Sentry for Jira Marketplace app redirects authentication to sentry.io, which only supports Sentry SaaS organizations.
The documented self-hosted installation method relies on installing the local Atlassian Connect descriptor.
However, Jira Cloud no longer supports installing new private Atlassian Connect applications using descriptor URLs on production sites, preventing the documented installation flow from completing.
To verify this was not an environment issue, I contacted both Atlassian Support and Sentry Support.
Atlassian confirmed that:
New private Atlassian Connect applications can no longer be installed via descriptor URLs on Jira Cloud production sites.
Development Mode no longer allows descriptor-based installations.
The recommended installation methods are Marketplace apps or Forge.
Sentry Support confirmed that:
The documented installation method for self-hosted Sentry is still the Connect descriptor (/extensions/jira/descriptor/).
The Marketplace app is intended only for Sentry SaaS (sentry.io).
Atlassian's retirement of descriptor-based installations blocks the documented installation flow.
There is currently no documented replacement installation mechanism for self-hosted Sentry.
As a result, I was unable to complete the integration despite meeting all documented prerequisites.
Event ID
No response