This page contains solutions targeted for developers.
Use the FAQ below to find answers to common questions. Feel free to contact our support team (email@example.com) if you don't see what you're looking for.
On every Git commit, make sure the message includes the exact issue ID at the beginning of the text. Git Integration Plugin for JIRA will automatically index new commits and associate the referenced issue.
To create a link between your Git commit and a JIRA issue, developers must include the issue key into the commit comment.
GIT-913 - Plugin version change from 2.6.7 to 2.6.8"; where GIT-913 is the issue key that links the commit message to the JIRA issue.
If you want to enforce the commit with a hook, please install this Git commit hook script .
Open the project summary in your browser and click on the Git Commits tab.
From "Select Version" drop-down, make sure that "All versions" is selected.
All changes that developers have submitted will be listed in reverse chronologically order. From this view, you can audit all of the changes that developers have recently submitted.
The commit retains the association even in the new project. The Git Integration for JIRA add-on supports history tracking. Thus, when moving a ticket to a new project whose issue key has changed, the association will still work.
The steps below provides an outline that you can follow to verify that the issue associations with commits are retained:
Yes – the Git add-on supports multiple JIRA issue keys in a multiple-line commit message.
For more information, see Smart Commits .