Skip to main content
Private preview. fremforge is in private preview — invited customers only. Content is still subject to change. Request access →
Integrations
Jira Cloud

Jira Cloud

Jira Cloud is Atlassian’s hosted issue tracker, addressed as https://<your-org>.atlassian.net/browse/<KEY>-<NUMBER>. This page wires commit messages, branch names, and PR titles in your fremforge repos to issue links in your Jira.

Forgejo side: external issue tracker

Repo Settings → “Advanced Settings” → External issue tracker.

FieldValue
External issue tracker URLhttps://<your-org>.atlassian.net/browse/{user}-{index}
External issue tracker URL formathttps://<your-org>.atlassian.net/browse/{user}-{index}
External issue tracker number formatRegexp
External issue tracker number format regexp([A-Z][A-Z0-9]+)-([0-9]+)

Apply, save. Every JIRA-123 or PROJ-456 (or whatever project key prefix your Jira uses) in commit messages, branch names, and PR titles becomes a clickable link to your Jira.

Recommended commit-message format

feat(api): add SBOM endpoint

PROJ-123 PROJ-124

Reference one or more keys at the end of the commit body. Jira’s “Development” panel on each issue picks up the linked commits via the inbound webhook (next section).

Tracker side: inbound webhook (optional)

To make Jira show the linked commits and PRs on each issue:

  1. Jira → Settings → System → WebHooks → Create a WebHook.
  2. URL: https://<your-org>.atlassian.net/rest/dvcs/1.0/jira-dvcs-webhook (replace with your tenant’s DVCS webhook endpoint; Atlassian’s docs at Linking commits to issues carry the current URL).
  3. Events: tick Push and Pull Request.
  4. In fremforge: Repo Settings → Webhooks → Add Webhook → Forgejo → paste the URL.

Verified payloads land in Jira’s DVCS Connector. Setup takes ~5 minutes per repo; cross-team admins typically wire it via Repo Defaults so every new repo inherits.

Sub-processor implications

Jira Cloud’s control plane is AWS US-east-1 + AWS EU-west-2 (Atlassian data residency picks one at signup). When you wire fremforge to Jira Cloud:

  • Commit messages + author email + repo name flow to Atlassian’s cloud.
  • Update your DPIA + sub-processor register to include Atlassian as a sub-processor handling Personal Data (commit metadata).
  • fremforge’s DPA explicitly excludes Atlassian — your tenant’s DPA addendum is a separate document.

If sovereignty is a hard constraint, use Jira Data Center (self-hosted) or Plane (self-hosted, EU-deployable, Apache 2.0) instead.

What this doesn’t do

  • No auto-close on merge (tracker-side automation: configure a Jira automation rule that closes the issue when the inbound webhook arrives with merged: true).
  • No bidirectional state sync (Jira issue moves to “In Progress” → fremforge branch is NOT auto-created; that needs a Forgejo Actions workflow on the customer side).
  • No smart-commit syntax (#close PROJ-123 doesn’t transition state — that’s a Jira-side automation rule the customer configures against the inbound webhook payload).
Jira Data Center