GitHub deployments not showing in Jira: what to check, in order
On this page
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:
-
Use a GitHub environment in the job. GitHub’s documentation says “By default, when a workflow job references an environment, GitHub creates a deployment object to track the deployment.” Check that the job’s
environment:block does not setdeployment: false, which opts out.jobs: deploy: runs-on: ubuntu-latest environment: production steps: - run: ./deploy.sh -
Call the API yourself, from a script or another CI tool: create a deployment, then, in Atlassian’s words, “call the create deployment status API […] at least once to update the status of the deployment”. GitHub accepts the states
error,failure,inactive,in_progress,queued,pendingandsuccess.
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:
- A separate deployment branch. A November 2025 thread describes CI running on separate dev and production branches. Check that the commits on the deployed branch still carry the key, especially if you squash or use release commits.
- Which commits count. Atlassian’s page walks through an example: a failed deployment still appears on the issues whose commits it carried, and the next deployment is linked to every commit that has not yet been deployed successfully.
- Large gaps. JRACLOUD-99064 (created 3 August 2026, Gathering Interest, 9 votes on 16 November 2026) reports that only the first 100 commits between two deployments are processed: “any commits beyond position 100 are silently dropped and never processed”. If only some issues from a big release are missing, count the commits between the two deployments. The workaround the ticket gives: “Deploy more frequently to keep the number of commits between any two deployments below 100”.
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:
- Atlassian: “You must have the space permission “View Development Tools” to see the Development panel in Jira work items.” Check that it is granted to those users.
- The space-wide list of deployments lives on the space’s Development page, under Deployments. That page follows the Development feature in Space settings > Features. Atlassian notes that turning the feature off doesn’t remove the Development panel on work items, so this explains a missing page, not a missing panel.
How to check the result
-
On GitHub, open Deployments and note the latest deployment and its state.
-
On Jira, open one issue whose key is in a commit of that deployment, then look for it in its Development panel.
-
Across a project, run JQL.
development[deployments].allis 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.
- A successful deployment is linked to every commit since the previous successful deployment of the same environment. It reads the range through GitHub’s API, page by page. We have tested this on a small test repository (14 September 2026), not beyond 100 commits between two deployments, so we don’t claim that it solves JRACLOUD-99064.
- Only
successtriggers that reading. A first deployment is linked to the 100 most recent commits of the deployed version. - A deployment that a newer one replaced still shows as deployed.
- Environment names are matched by fixed rules: names containing
stag,preprod,pre-prodoruatare Staging, thenprodis Production,testorqaTesting,dev,previeworreviewDevelopment. There is no.jira/config.ymlsupport: other names show as Unmapped. Atlassian’s app is more flexible on this point. (Until version 2.28.0, released 16 November 2026,preprodwas wrongly sent as Production.) - Deployments arrive by webhook only. One missed while a webhook was down is not caught up later.
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.
More guides
- How to connect GitHub to Jira Cloud
- GitHub Issues vs Jira
- GitHub commits not showing in Jira
- GitHub for Jira backfill: restart it and check it
- Jira Smart Commits with GitHub: syntax and checks
- GitHub for Atlassian is moving to Forge: what to check
- Limit which GitHub repositories each Jira project can link
- JQL for GitHub data in Jira
- Linkwright permissions and sync statuses, explained
- GitHub for Jira alternatives
- 24 hours side by side with GitHub for Atlassian
- GitHub organization not showing in Jira