feat(jira): support Jira Cloud via Atlassian API Gateway - #9024
Merged
klesh merged 1 commit intoJul 30, 2026
Conversation
- Add JIRA_GATEWAY_REGEX and a third connection mode 'Jira Cloud (Atlassian API Gateway)' in the connection UI - Auto-build endpoint from Cloud ID input: the user types only the Cloud ID and the full gateway URL is constructed automatically - Force authMethod=AccessToken for gateway connections; existing BasicAuth path for standard cloud and server connections is unchanged - Detect gateway endpoints on edit/load and pre-fill the Cloud ID field - Suppress misleading /rest/ hint in testConnection() for api.atlassian.com endpoints (a 404 there means a bad Cloud ID, not a missing /rest/ path) - Add unit tests for gateway and standard-cloud connection flows - Add frontend test suite for regex patterns and Cloud ID builder No migration script required. No new DB columns. All collectors, extractors, converters and domain models unchanged.
klesh
approved these changes
Jul 30, 2026
klesh
left a comment
klesh
left a comment
Contributor
There was a problem hiding this comment.
LGTM.
Thanks for your contribution.
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
2 participants
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.
Summary
Adds support for connecting to Jira Cloud through the Atlassian API Gateway endpoint (https://api.atlassian.com/ex/jira/{cloudId}/).
Some organisations access Jira Cloud through this gateway URL rather than the standard https://.atlassian.net/ endpoint, using service accounts with scoped API tokens. The existing connector assumes the standard endpoint and produces unhelpful error messages when the gateway URL is used.
Changes
Backend - backend/plugins/jira/api/connection_api.go
Frontend - config-ui/src/plugins/register/jira/connection-fields/auth.tsx
Tests
Backward Compatibility
No database migration required. No new columns. The endpoint and token fields in _tool_jira_connections store the gateway URL and scoped token respectively - both already exist and are encrypted at rest. All collectors, extractors, converters, domain models, incremental sync, and Grafana dashboards are unchanged.
How to Test
Mock test (no credentials needed):
cd backend && go test -timeout 60s -v ./plugins/jira/api/...
UI test:
Find your Cloud ID at admin.atlassian.com - Settings - Organisation.