Git Integration for Jira Cloud Documentation

Linking git commits to Jira issues

Link your git commits to Jira issues by including the issue key in the commit message.

On this page:

 


 

Understand Commit Linking

Git Integration for Jira selects commits by issue key. Include issue keys in your commit messages every time you commit.

Example: The commit message “PRJ-50 fixed issue” links to issue #50 in the PRJ project. This assumes you have a Jira project with the key “PRJ” and someone created issue #50 within that project.

Example: The commit message “TEST-1 Update…” links to Jira issue TEST-1.
Commits from non-master branches appear only if the master branch does not contain them.

 

Follow Best Practices for Linking

When working with sub-tasks, include both the parent and sub-task issue keys in your commit message. This approach:

  • Displays the commit in both places
  • Prevents sub-task commits from getting lost among parent issue commits

The maximum commit message length is 8,000 characters.

Support for Renamed Projects

Git Integration for Jira supports commits that use the old Jira key after a project rename (for example, TEST-16 to PROJ-16).

Two scenarios apply after a rename or move:

  • The Jira project key was renamed and the commit message contains the old key (from before you installed Git Integration for Jira)
  • A Jira issue was moved to another project and the message contains the old key (from before you installed Git Integration for Jira)
Jira Activity Stream: Only commits linked to Jira issues appear in the Activity Stream—not all commits from connected repositories.

 


 

Associate Commits Manually

These steps apply to Jira Cloud instances with Git Integration for Jira installed.

Access the Change commit issues feature from two locations:

From the Issue Page:

  1. Open the issue page.
  2. Go to the Git Commits tab.
  3. Click View Full Commit.
  4. Click the edit icon to modify associations.

From the Repository Browser:

  1. Go to AppsGit Integration: Repository browser.
  2. Click a repository that contains commits.
  3. Click the edit icon on the commit you want to modify.

Method 1: Use the Dropdown

  1. Click the dropdown arrow in the Associated issues to commit field.
  2. Select a Jira issue from the list.
  3. Repeat to associate additional issues.
  4. Click X next to an issue to remove that association.
  5. Click Save to apply changes.

Method 2: Type to Search

  1. Type a Jira issue key or a word from an issue summary.
  2. Select a matching issue from the results.
  3. Repeat to associate additional issues.
  4. Click X next to an issue to remove that association.
  5. Click Save to apply changes.

Association Permissions

Jira administrators can add or remove any associations.

Project administrators can add or remove associations within their projects.

Commit authors can add or remove their own associations if they have View Development Tools access.

Multiple Associations

If a commit is associated with multiple Jira issues, you see all linked issues in the dialog:

In this example, the commit is associated with issues TEST-1 and TEST-4.

Saving changes triggers a repository reindex to display the new associations.

 


 

Link Branches to a Jira Issue

Include the Jira issue key in the branch name when you create a new branch.

Create a Branch in Your Git Service (GitHub Example)

  1. Click the branch dropdown (showing master or your current branch).
  2. Enter a new branch name that includes the Jira issue key.
  3. Click the result to create the branch.

Create a Branch from Jira

  1. Open a Jira issue.
  2. Click Git Integration in the right sidebar.
  3. Click Create branch.
  4. Select a repository.
  5. Select the source branch to use as a base.
  6. Edit the proposed branch name if needed, but keep the Jira issue key.
  7. Click Create branch.

 


 

Link Pull or Merge Requests to a Jira Issue

Include the Jira issue key in the pull request title or description when you create a new PR/MR.

Create a Pull Request in Your Git Service


  1. Set the base and compare branches (for example, feature branch to master).
  2. Enter a title that includes the Jira issue key.
  3. Optionally, include the Jira issue key in the description for additional linking.
  4. Submit the pull request.

Create a Pull Request from Jira

  1. Open a Jira issue.
  2. Click Git Integration in the right sidebar.
  3. Click Create pull request (or Create merge request for GitLab).
  4. Select a repository.
  5. Select the source branch.
  6. Select the target branch.
  7. Edit the proposed name if needed, but keep the Jira issue key.
  8. Submit the request.

 


 

Prev: Web linking

Next: Smart commits

 

Last updated: December 2025

Have feedback about this article? Did we miss something? Let us know!
On this page