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

Integrations

Most teams adopting fremforge already have an issue tracker — Jira, Azure Boards, Linear, Trello — and want their code changes to link back to the tickets that motivated them. fremforge’s underlying Forgejo platform ships an external issue tracker primitive that handles the one-way clickable-link case with zero engineering: drop a URL pattern into repo settings and every JIRA-123 in a commit message, branch name, or PR title becomes a clickable link straight to your Jira (or Azure DevOps, or Linear, or Trello card).

This section is the how-to for the seven most-asked-about trackers. Each page is ~50 lines and covers:

  1. Forgejo side — the URL pattern, regex, and repo-setting fields.
  2. Tracker side — the optional inbound webhook (PR/commit notifications appear in your tracker too).
  3. Commit-message conventions — the syntax your engineers use to make the link fire (e.g. [JIRA-123], AB#456, LINEAR-789).
  4. Sub-processor implications — when commit metadata crosses an organisational boundary, what that means under your fremforge DPA.

Pick your tracker

  • Jira Cloud — Atlassian-hosted (*.atlassian.net).
  • Jira Data Center — self-hosted Jira on your infra.
  • Azure Boards — Microsoft’s tracker, part of Azure DevOps.
  • Linear — Linear.app cloud tracker.
  • Trello — Atlassian’s card-based tracker.
  • Plane — self-hosted open-source issue tracker (Apache 2.0).

What’s NOT here

  • Automatic state transitions (“close JIRA-123 when PR merges”) — fremforge does not (yet) auto-transition issue state in your external tracker. The link goes one way: commit/PR/branch → tracker. The reverse (tracker UI shows linked commits) lands via the inbound webhook each tracker provides; configure it on the tracker side per the per-page instructions.
  • Custom field sync — fremforge does not write to tracker custom fields, sprints, epics, or work-item hierarchies. These are tracker-internal concepts that vary too much to standardise.

If your workflow depends on auto-close on merge, two options:

  1. Tracker-side automation — every tracker above can be configured to close an issue when a webhook arrives with a specific payload. Wire fremforge’s outbound webhook (admin → Webhooks) to your tracker’s automation endpoint and write the close-rule there.
  2. A Forgejo Action in your repo — drop a step that POSTs to your tracker’s REST API on pull_request.closed with the merged: true filter. Five-line workflow file. We may ship a templated version of this in a future release; for now it’s a customer-side build.

Sub-processor footprint

Connecting commit metadata to an external tracker means commit messages (and their authors) flow to that tracker’s cloud. For tracker-side hosted services that’s a new sub-processor relationship under your fremforge DPA. The per-tracker pages name the relevant control plane (US / EU / hybrid) so your DPIA can list it correctly.

Self-hosted trackers (Jira DC, Plane) are not sub-processors — the metadata stays inside your own perimeter.