Linkwright

GitHub for Jira backfill: what it imports, how to restart it, how to check it

When you connect GitHub to Jira Cloud, the connector does not only link what happens from now on: it also goes back through your repositories and imports past branches, commits and pull requests. In GitHub for Atlassian (the free app many teams still call “GitHub for Jira”) this is called the backfill. This page sums up what Atlassian documents about it, read on 1 November 2026, how to restart it, and how to check that it really brought your history in.

What the backfill imports

From Atlassian’s page Backfill GitHub data in Jira:

So a commit that does not name an issue, or that only lived on a branch you deleted, will never appear, however long the backfill runs. That is the first thing to rule out when history looks incomplete.

How long it takes

Atlassian’s FAQ says that for an organization with little data, backfilling “may only take a few minutes”. For a larger one, the app’s own screen warns that going further back “may take a long time and can slow down other sync work”. GitHub’s API rate limit is the usual reason: a GitHub App gets 5,000 requests an hour as a base, up to 12,500 for large installations, and a backfill has to share them with day-to-day sync.

How to continue or restart a backfill

The documented path, as of 1 November 2026:

  1. In Jira, go to Apps › Manage apps, then GitHub for Atlassian.
  2. Open the settings menu (…) of your GitHub organization and choose Continue backfill.
  3. Pick the date to backfill from, then Backfill data.
  4. To redo the import from scratch rather than extend it, tick Restart the backfill first. Atlassian describes this as overwriting the existing historical data.

The same screen shows a status per organization: Pending, In progress, Finished or Failed. For a failure, the app says it “will automatically retry”, and offers a retry button next to the status if it does not. It also reports how many repositories could not be completed, and lists the status of each backfill task (pull requests, builds, deployments…) per repository. The causes it names: permission issues, GitHub API rate limiting or network outages.

“Finished” does not prove your history is there

A finished backfill tells you the job ended, not what it brought in. Atlassian’s own tracker has an open request about exactly this: JRACLOUD-99641 (created 25 September 2026, “Gathering Interest”) asks for clear backfill status and sync summary metrics, because the backfill can end with a generic “FINISHED” status even when nothing was ingested.

To check for yourself, in five minutes:

  1. Pick three issues you know well: one with commits on the default branch, one whose work happened on a feature branch, one older than a few months.
  2. Count in GitHub: search the repository for the issue key in commits and pull requests.
  3. Count in Jira: open each issue’s Development panel. Atlassian documents that it shows only the first 100 commits of an issue, so for a long-running issue compare up to 100.
  4. Count across a project with JQL, for example project = CHK AND development[commits].all > 0 (more queries in JQL for GitHub data in Jira). Run it before and after the backfill: the number of issues should go up, not stay flat.
  5. Explain each gap before blaming the backfill: no key in the message, a deleted branch, more than 50 commits on a non-default branch, or a date older than the backfill start.

What you cannot do today

Three open requests on Atlassian’s public tracker, read on 1 November 2026, describe current limits:

Request What it asks for Status
JRACLOUD-99984 (28 Oct 2026) A public REST API to trigger, restart or monitor a backfill. Atlassian’s description: “Currently, there is no public REST API available in Jira Cloud” for it. Gathering Interest, 0 votes
JRACLOUD-94184 (22 Apr 2025) Re-sync only the affected repositories during a manual backfill Gathering Interest
JRACLOUD-96218 (29 Sep 2025) Turn the backfill off Gathering Interest

In practice: a backfill is started by hand from the settings screen, for a whole organization, and its result is checked by hand.

Does the Forge migration mean a new backfill?

Atlassian is moving GitHub for Atlassian to Forge, with a production rollout in October 2026 and “post-rollout verification” in November and December. Its migration page says your “connected GitHub organizations, repositories, and settings will carry over automatically”. It does not say whether past development data is kept as is or imported again. The safe move is the before/after count above; see GitHub for Atlassian is moving to Forge.

How Linkwright handles history

Linkwright imports less history than GitHub for Atlassian, by design, and says so. On the first read after a repository is attached to a Jira project, and again on every Refresh, it catches up:

It does not go back six months. What it adds is visibility: each repository shows its state (Up to date, Out of date, Webhook down, Rate limited, Failing, Not authorized) with the time of its last successful read, and the Refresh button rereads one repository on demand, without restarting a whole organization. In our side-by-side test on 1 October 2026, GitHub for Atlassian caught up history pushed before connection better at first (3 commits out of 3, against 2 for us); after a fix the same day, Linkwright caught up 3 out of 3 as well.