Setup & usage guide
Azure Git Listener is available for all Jira Cloud installations. Sign in to your Jira account, open the Azure Git Listener for Jira page on the Atlassian Marketplace, and click Install.
After installation you'll be prompted to configure Azure Git Listener. You can also reach the configuration page at any time: open your organization's app management page, select the appropriate Atlassian site and open the Connected apps section. Find Azure Git Listener in the list of installed apps, click the three-dot menu on the right and choose Configure.
To link your Azure repositories, select your Azure DevOps instance type (Cloud or Self-hosted), enter your Personal Access Token (PAT), and click Save. The token must include Code (Read) permissions and be scoped to All accessible organizations.
Azure Git Listener automatically detects the repositories your Microsoft account can access and lists them on the configuration page. Choose which repositories to link and view when each was last checked for updates. To update or replace your PAT, return to the configuration page and update your integration settings.
Use scoped, least-privilege tokens. Azure Git Listener reads metadata only and never clones your code. See the security overview.
Once configuration is complete, open any issue in your Jira project and you'll see the Azure Git panel on the right. Expanding it shows all commits, branches and pull requests associated with the issue.
Linking is performed using issue keys (e.g. PROJ-123) — include the issue key in commit messages, branch names and pull-request titles so items are detected correctly.
Besides its own panel, Azure Git Listener can feed Jira's built-in Development panel — the one Jira's native integrations use — with the commits, branches, pull requests, builds and deployments it syncs from Azure DevOps. Your team sees Azure DevOps activity in the familiar place, and the Azure Git panel keeps working alongside it.
To turn it on, open the configuration page, switch to the Settings tab and enable Jira development information. The Status card shows whether Jira has granted the app access, how many of your linked repositories have been pushed to Jira, and when the last push happened.
Jira grants the app access in the background, usually within five minutes of installing or upgrading. If the status stays at Waiting for Jira, a Jira administrator may need to approve the latest version of Azure Git Listener under Apps → Manage apps.
Once enabled, the Development section of every issue lists the branches, commits and pull requests that mention the issue key, together with the Azure Pipelines builds and deployments of the commits behind them. Changes are pushed to Jira every few minutes. Turning the setting off stops the Development panel sync; the Azure Git panel keeps working either way.
Builds and deployments are read from Azure Pipelines with the same Personal Access Token, so it also needs Build (Read) and Environment (Read & manage) permissions on top of Code (Read).
If you have any questions or need assistance, please contact us via our feedback form.
Pick the platform you work in — every plan includes a free trial on the marketplace.
AWS
GitLab