Linkwright

GitHub deployments not showing in Jira: what to check, in order

Your commits, branches and pull requests appear on Jira issues, but the Deployments tab is empty, or a deployment lands on an environment called “undefined” or “Unmapped”. The connection works, so this is rarely a connection problem. It comes from how deployment data reaches Jira. This page sums up what Atlassian documents for GitHub for Atlassian, read on 16 November 2026, in the order that rules out the most causes first.

1. Pending permissions on an older installation

This is the cause with the shortest fix. In a June 2026 community thread, everything was linked except deployments. The author’s conclusion: the app “was installed so long ago that it was missing permissions. After granting them the Deployments tab began showing data.”

Ask a GitHub organization owner to open the list of GitHub Apps installed on the organization, in its settings, and see whether the Atlassian app is waiting for new permissions to be accepted. We found no page that shows this from the Jira side.

2. GitHub never created a deployment

Atlassian’s page is precise: “The GitHub for Atlassian Marketplace app only listens to deployment_status events.” A workflow that builds and ships your code does not create one by itself. There are two ways to get one:

To check, open your repository on GitHub and look at the Deployments page. If it is empty or has no recent entry, Jira has nothing to show and the fix is on the GitHub side.

3. No issue key in what was deployed

A deployment does not name an issue. Jira finds issues by “scanning deployed branches for new commit messages that contain Jira work item keys”, and Atlassian says you “must include Jira work item keys in commit messages, branch names, and pull requests.”

Three cases catch people out:

4. “undefined” or “Unmapped” environment

If deployments arrive under the wrong environment or none, it’s the name. “Jira tries to guess which environment to map your deployment event to based on the environment name”, and otherwise “Jira will show these as undefined environments.”

The text matches, as listed on JRACLOUD-89992 (64 votes):

Jira environment Names that match
Development development, dev, trunk
Testing testing, test, tests, tst, integration, integ, intg, int, acceptance, accept, acpt, qa, qc, control, quality
Staging staging, stage, stg, preprod, model, internal
Production production, prod, prd, live
Unmapped no match

Names of your own, like eu-west or customer-a, need a mapping. Add a file called .jira/config.yml to the main branch of the repository:

deployments:
  environmentMapping:
    development:
      - "dev*"
    testing:
      - "qa-*"
    staging:
      - "stage-*"
    production:
      - "eu-west"
      - "customer-*"

Two rules from Atlassian’s page: “Once you add this configuration file, Jira will not be able to automatically detect environment names”, so list every environment. And “You can specify up to 10 glob patterns for each of the four valid environments in Jira.” The structure above follows the example on Atlassian’s page; the names are examples of ours.

5. Jira hides it from you

If deployments exist but some people don’t see them:

How to check the result

  1. On GitHub, open Deployments and note the latest deployment and its state.

  2. On Jira, open one issue whose key is in a commit of that deployment, then look for it in its Development panel.

  3. Across a project, run JQL. development[deployments].all is refused by Jira Cloud, but this one works (checked on our test site, 16 November 2026; more in JQL for GitHub data in Jira):

    project = ABC AND deploymentEnvironmentType is not EMPTY
    

Run the query before and after a deployment you know touched a given issue.

Questions that come up after that

Why does a rolled-back release still look deployed? Redeploying an older commit usually adds no new commits to scan, so the issues keep their status. GitHub’s deployment states include no “rolled back” value.

Why does a feature-branch deployment re-link old issues? A thread with over 3,200 views reports deployments from feature branches re-associating work. Deciding which branches deploy to which environment in your workflow, for example with deployment: ${{ github.ref_name == 'main' }}, limits what Jira receives.

Is only the tagged commit marked as deployed? In the Atlassian-documented behaviour above, no: every new commit with a key counts. A report of the contrary is worth comparing against section 3.

How Linkwright handles deployments

Linkwright is a paid Forge app for GitHub.com and Jira Cloud, made by the author of this page, so read this section with that in mind. It listens to the same deployment_status event, so sections 2, 3 and 5 apply to it as well.

What it adds is the status of each repository (Up to date, Webhook down, Not authorized and so on), so you can tell whether the data stopped arriving or never existed.