Changelog
What changes for people using Linkwright for Jira, newest first.
16 November 2026 — version 2.28
- Pre-production environments. A GitHub environment named
preprodorpre-prodwas sent to Jira as Production, because its name contains “prod”. It is now sent as Staging, as intended (checked on our test site with a real deployment). Deployments already sent are not sent again.
6 November 2026 — version 2.27
- Pushes beyond 10,000 commits. GitHub stops comparing at 10,000 commits without an error. A new branch of 10,500 commits was read up to that limit and reported as a success, leaving 500 commits unlinked with no warning. We found this on our own test site, the same day as 2.26. Those commits still aren’t linked, but the repository now shows “Commits unread”.
6 November 2026 — version 2.26
- Commits that could be missed. We measured two cases where commits were not linked, with no warning: a first push to an empty connected repository (900 of 1,000 commits missed) and a new branch of 4,000 commits (none linked). Both are now read in full, as is a new branch with no common ancestor.
- Unread commits. If a push cannot be read to the end, the repository no longer shows as up to date: a status says so until that push has been read in full.
6 November 2026 — version 2.25
- GitHub authorization. When GitHub no longer accepts your authorization, because it was revoked or has expired, Git sync health now says so and offers a button to authorize again. Before, the button repeated the error, or the page showed a raw platform error with no way forward. Synchronization of commits does not depend on this authorization and kept working.
- Logs. Email addresses are removed from the branch and environment names we log.
5 November 2026 — version 2.24
- Branch name format. A project administrator can choose the format of the branch name proposed on
its issues, from
{key},{description}and{type}, under Space settings › Apps › Git repositories. A format that would not link a branch to its issue, or that Git would refuse, is not saved. The app still creates no branch. - Issue keys in descriptions. A description citing another issue key no longer links a second issue.
- Logs. Email addresses are removed from all the Jira refusals we log.
5 November 2026 — version 2.23
- Get started. The menu of Linkwright under Site settings › Connected apps now has a Get Started entry, opening the same page as Git sync health.
- Large accounts. New links are written together rather than one by one, one issue cited by thousands of commits stays readable, and suggestions are read faster after an organization is connected, with the page saying how many repositories have been read so far.
- Issue panel. Above 10 repositories in a project, it lists those holding this issue’s links and counts the others.
- Nothing lost in silence. When Jira could not be told about commits because the queue refused them, a full send is now owed and the screens say so. A repository whose check keeps failing no longer holds up the others.
- Logs. Email addresses are removed from most of the Jira refusals we log.
5 November 2026 — version 2.22
- Security fixes. A repository can now be detached only by a project it is attached to. Nothing of a Jira site is kept in memory between two calls, so a process reused for another site can’t verify its webhooks with the wrong secret. Once a GitHub account is disconnected, the daily suggestions stop reading its repositories. A deployment link on an issue must be an http(s) address.
- Screens. Menu names match what Jira shows today, and the message after disconnecting an account with no attached repository is worded correctly.
5 November 2026 — version 2.21
- Admin actions check the caller’s Jira permissions. Every action behind the admin screens now asks Jira whether the person is an administrator of the site or of the project, and refuses otherwise. Before this, the app relied on the screen being reachable only by administrators.
- The Jira admin no longer has to be the GitHub owner. Create an invitation link in Git sync health and send it to an owner of the organization. It works once, for that organization only, and expires in 72 hours. The owner needs access to Jira on your site, but doesn’t need to be an administrator.
- Authorized the wrong GitHub account? Use another GitHub account now lets you choose.
- Same branch name in two repositories. Deleting it in one repository no longer marks it deleted in the other, on the issue panel or in Jira’s Development panel.
- More failures are shown. When Jira refuses or loses what a repository sends, or a webhook could not be created, the repository says so with the reason, instead of looking up to date. Limits a first read ran into are listed next to Up to date.
- Large accounts. Installations of more than 500 repositories are listed in full, up to 5,000. Readings are spread over 5 minutes, and a GitHub secondary rate limit is no longer read as a revoked access.
- Refresh on a large repository. Above 400 items, Refresh re-reads GitHub without rebuilding what Jira holds, and the screen says so.
- A branch name to copy. The issue panel suggests one that contains the issue key.
5 November 2026 — version 2.20
- A broken webhook now says so. When at least 3 commits appear on a repository’s default branch with no webhook behind them, its state turns Webhook down, with what to check on GitHub. Commits from before you attached the repository never count, a late delivery is given 15 minutes, and any delivery clears the state. Until now this state could not appear. How it avoids false alarms.
4 November 2026 — version 2.19
- Proof that sync happened. Under each repository, on “Git repositories” and “Git sync health”: “Last delivered to Jira: commit abc1234, 3 min ago”, the last commit Jira accepted. When nothing has been sent yet, the screen says “Nothing delivered to Jira yet”.
- Search and filters. Find a repository by name, and narrow the list to Needs attention or Not checked yet. When no repository needs attention, the screen says so.
- A reading in progress counts itself. After attaching a repository or clicking Refresh, the screen shows “Reading 1 of 2 repositories…” with a progress bar and updates itself when done: no more reloading the page.
- What each permission and status means, on one page: Permissions and sync statuses, explained.
2 November 2026 — version 2.17
- Smart Commits run. A
#comment,#timeor transition command in a commit message is now run by Jira, as with Atlassian’s integration. For safety, only for a commit you wrote and pushed yourself (GitHub must have verified its email address on the account that pushed it), whose issue keys all belong to projects the repository is attached to, and only when it arrives live: history read later is never replayed. Details: Smart Commits guide. - Automatic transitions come from live activity only. Commits re-sent to Jira later (first read after attaching a repository, periodic re-read, Refresh) no longer trigger your Jira workflow’s automatic transitions.
2 October 2026 — version 2.13
- When GitHub takes a repository away from the app, the page says so, and says why. If a repository is removed from the GitHub App’s repository access, renamed or deleted, “Git repositories” shows it as Not authorized as soon as the page is opened, with what to do: add it back under Repository access, or detach it. Links already in Jira are kept. (Measured side by side the same day: with access removed, the official connector erased the issue’s commits from Jira without a word.)
- Attached repositories are re-read every 30 minutes instead of 15, as a safety net behind webhooks, which still deliver every change as it happens.
2 October 2026 — version 2.12
- Uninstalling cleans up after itself. Before Jira removes the app, it now deletes the webhooks it created on your GitHub repositories. Previously they stayed behind, pointing at an address that no longer existed.
1 October 2026 — version 2.11
- Buttons say what they are doing. Connecting a GitHub organization, attaching and detaching each wait on GitHub for a few seconds; the button now reads “Looking for your GitHub installations…”, “Connecting…”, “Attaching…” or “Detaching…” meanwhile, instead of looking like a click that did nothing.
- An attached repository’s row updates by itself a few seconds later, once its first reading is done.
1 October 2026 — version 2.10
Found by installing the app on a brand-new Jira site and going through it the way a new customer would.
- An attached repository is read at once. It used to wait for the next scheduled pass and say “never reconciled” for up to five minutes, next to commits that had already arrived.
- Empty repositories work. A repository with no commit yet failed every reading; it is now simply up to date.
- The first screen explains its wait. Right after installation the app prepares its database, which takes a few seconds; the screen now says so instead of staying blank, and the preparation starts as soon as the app is installed.
- Wording: an unattached repository with no ignored activity no longer reads “activity ignored never”.
1 October 2026 — version 2.9
- A repository added on GitHub shows up within seconds. Opening Git sync health or a project’s Git repositories page now looks for repositories added to the GitHub App since the last check, and the page updates itself. Measured: 2.9 seconds. Before, it could take up to 10 minutes.
1 October 2026 — version 2.8
- Every send is now checked, not only full ones. Five minutes after commits reach Jira from a push, the app reads back what Jira kept and repairs any link it dropped. Before, only a full resend was checked.
- Large repositories are checked too. Past 400 items Jira answers with a sample; the app now judges the commits that sample holds instead of giving up.
- Dependencies updated: two advisories in transitive packages fixed.
1 October 2026 — version 2.7
- Refresh now repairs branches too. Jira can drop a branch from an issue while keeping it stored; resending it does not bring it back. A full send now deletes the branches Jira holds, waits until Jira confirms the deletion, then creates them again — the way commits were already repaired. Measured on our test site: 30 branches and 20 pull requests back on their issue.
1 October 2026 — version 2.6
- Older commits on feature branches are caught up. On the first read after a repository is attached, and on each Refresh, the app reads the commits that up to 20 branches it has not seen yet hold beyond the default branch. Before, only the default branch’s history was caught up.
1 October 2026 — version 2.5
- New repositories appear within 10 minutes of being added to the GitHub App, instead of up to an hour.
- Bursts of activity are handled faster. A push updating 30 branches now reaches Jira in about a minute; before, the burst could saturate the app’s storage, and the last links took three to four minutes to arrive.
- Guided setup. The administration page shows a checklist of the setup steps, computed from what the site actually holds, with a link to install the GitHub App.
- Suggested repositories. A project’s settings page lists first the repositories whose recent commits cite that project, with a button to attach them all.
- Clearer refusals. When the person connecting a GitHub organization is not one of its owners, the page says so and explains who can do it.
- Sync health counts attached repositories only. A repository no project uses is no longer reported as “never synced”.
30 September 2026 — version 2.1
- Disconnecting a GitHub organization detaches all its repositories and removes their webhooks and Development panel entries; it can be safely retried.
- Attaching or detaching a project on a repository shared by several projects updates the issues of that project only.
- Failed removals are retried automatically, a few repositories at a time.
- A repository detached from its last project and attached again sends its history to Jira again.
September 2026 — first versions
- Commits, branches, pull requests with reviews, and deployments in Jira’s native Development panel, so JQL, boards and Automation work as usual.
- A sync state for every repository, with its last webhook and its last successful check, and a Refresh button.
- A check five minutes after sending that Jira kept the links of a full send, with repair.
- Repositories scoped per Jira project, connected by an owner of the GitHub organization.
- English and French interface.