Gitea Integration for Jira

Atlassian Forge app

Gitea development activity, on the Jira issue.

Gitea Integration for Jira connects a Jira Cloud site to a Gitea instance you operate. Commits, branches and pull requests that mention an issue key show up on the issue and in Jira's built-in Development panel. Smart-commit commands work from Gitea commit messages.

Atlassian Marketplace Support

Prerequisite

Public HTTPS Gitea required

The app requires a Gitea instance reachable over the public internet via HTTPS. Forge runs on Atlassian's infrastructure and must call your Gitea API and receive webhooks. Private-network or HTTP-only Gitea is not supported.

What it does

Self-hosted Gitea, without leaving Jira.

Teams that keep source on Gitea still plan work in Jira. This app is the bridge: it does not host your Git data, and it does not send it to us. It talks only to your Gitea and to Jira APIs, from Atlassian Forge.

Issue panel
Linked commits, branches and pull requests on the Jira issue, with status lozenges and links back to Gitea.
Development panel
The same activity is pushed into Jira's built-in Development panel via the Forge DevInfo provider.
Smart commits
#comment, #time and #transition in Gitea commit messages. Comments author as the app.
Create branch
Open a branch on a linked repository from the issue, using the issue key in the branch name.

Setup

Connect once. Link the repos you care about.

  1. 1

    Install from Marketplace

    A Jira administrator installs the app on the Cloud site. Marketplace licensing is enforced by Atlassian.

  2. 2

    Create a Gitea OAuth2 application

    On your Gitea, register an OAuth2 application and paste the redirect URI shown in the app's settings. The app stores the client id and secret in Forge SQL for that site only.

  3. 3

    Authorize

    An admin completes OAuth. The app keeps access and refresh tokens in Forge SQL. They never reach the browser.

  4. 4

    Link repositories

    Pick repositories to watch. The app registers a signed webhook on Gitea and shows the delivery URL. Pushes, branch changes and pull-request events then update Jira.

Data

No vendor backend. No analytics.

All app data lives in Forge hosted storage (Forge SQL), per installation, operated by Atlassian. We do not run a separate database, CDN analytics, or tracking pixel.

Privacy policy  ·  Data retention

Availability

Standard edition, paid via Atlassian.

Pricing is per Jira user per month, billed by Atlassian. Sites on Jira Cloud Free (1–10 users) are $0, as Marketplace policy requires. Paid tiers are $3.50 per user per month, with Atlassian's standard annual option (10 months for 12).

Support is email-only at gitea-jira@wsagency.io, SLA 1–2 business days.