Git Listener Documentation

Learn how to install, configure, and use Git Listener for Jira

← Back to Product Page

Installation

Git Listener is available for any Jira Cloud installation. Just log in to your Jira account, go the Git Listener for Jira Atlassian Marketplace page, and click the button to install the plugin.

Configuration

After installation, you will be prompted to configure Git Listener.
You can also access the configuration page at any time by navigating to your organization’s app management page, selecting the appropriate Atlassian site, and opening the Connected apps section. Locate Git Listener in the list of installed apps, click the three-dot menu on the right, and select Configure.

To link your Azure repositories to Jira, 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.

You will be able to choose between different Git providers and different authorization methods. Follow the instructions on each provider's page to link your Git account to Jira.

Git Listener will automatically detect all Git repositories that your account has access to and display them on the configuration page. You can configure which of the repositories you want to link to Jira, and see when Git Listener last checked them for new data.

If you need to update the token used to link Git Listener to your repositories, or change the user who needs to grant OAuth permissions, you can always return to Git Listener configuration page and click "Re-configure integration".

Using Git Listener for Jira

As soon as the configuration is finished, you are ready to use Git Listener. Just navigate to any issue in your Jira project, and you will see Git menu option on the right.

Click on it, and it will display all the Git commits, branches, and pull requests linked to your Jira issue. Linking is done via issue keys (e.g. PROJ-123). That means you will need to include issue keys in your commit and pull request titles, and branch names in order for them to be picked up by Git Listener.

Further information

Feel free to contact us via our feedback form if you have any questions.