Git Integration for Jira Self-Managed (Data Center/Server) Documentation

Contact Support
GitKraken Status  

Manually link git commits to Jira issues

Right click here to open this video in a new browser tab for more viewing options.

 

The process steps in this section applies to Jira Server/Data Center/Cloud with installed Git Integration for Jira app.

To manually link a git commit to a Jira issue, access the Change commit issues feature from the following locations:

  • Project page ➜ Git Commits ➜ click View Full Commit on the commit panel.

  • Issue page ➜ Git Commits tab ➜ click View Full Commit on the commit panel.

  • Git menu ➜ View all repositories ➜ click a repository with git commits.

View full commits dialog highlighting the change commit issues function

Click the Change commit issues label. The following dialog is displayed.

This is the commit association dialog where you can manually map or associate a commit to a Jira issue. The setting shows one Jira issue key association.

Add, edit or delete linked Jira issue keys in the Associated issues to commit field.

  • JIRA administrators can add/remove any association.

  • Project administrators can add/remove any association in that project.

  • The authors of the commit can add/remove the association, if they have the View Development Tools access.

If the commit is associated with multiple Jira issues, you will see the following:

This is the commit association dialog where you can manually map or associate a commit to a Jira issue. The setting shows multiple Jira issue key associations.

In the above example, the selected commit is associated with Jira issues TEST-1, TEST-2 and PROJ-4 separated by commas.

Using the above example:

  • To associate the commit to an issue, insert a new issue key separated by a comma.

  • To remove commit association to an issue, delete the issue key.

Click Save to save the changes.

Saving the changes triggers a repository reindexing to show new associations.

 


Prev: Linking git commits to Jira issues

Next: Git notes

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