| Info |
|---|
If you are interested in TFS / VisualStudio Team Services check-ins synchronization you may be also interested in our open source JIRA issue key check-in policy plugin for Visual Studio. Please take a look at its home page for further details. |
| Table of Contents |
|---|
Associating Check-In With a
...
Jira Issue
Associating using a check-in comment
Associating a TFS / Azure DevOps (formerly VSTS) check-in with a JIRA Jira issue is very simple and straightforward. The only thing that you have to do is type an issue key as a part of your TFS / Azure DevOps (formerly VSTS) check-in / Git commit message, as shown below. .The key can be anywhere in the comment.
This is the standard JIRA Jira way of associating sources with issues, the same method is used in other types of source code repositories (e.g. Subversion).
Associating using a check-in note
It is also possible to associate a check-in with a JIRA Jira issue by typing an issue key as a part of any check-in note associated with the check-in. Name of the check-in note is not important - all notes are scanned, but it may be a good idea to name the check-in note accordingly and perhaps even make it mandatory in order to enforce a JIRA Jira integration policy.
Associating using TFS / Azure DevOps (formerly VSTS) Work Item
If you have properly set up your TFS4JIRA Synchronizer application to perform TFS / Azure DevOps (formerly VSTS) to-and-from JIRA Jira issues synchronization and (in case of JIRA Jira Cloud environment) exposed it to web requests from the internet Internet (see Settings for JIRA Cloud), associating check-ins with JIRA Jira issues is even easier - actually it is fully automatic. All you need to do is associate your check-in with a TFS / Azure DevOps (formerly VSTS) work item and the Synchronizer will take care of the rest - it will find the work item's matching issue and when you open that issue it will display the changesetchange-set.
Scanning of changesets change-sets associated with a JIRA Jira issue synchronized to a work item is done "lazily" for performance reason, because retrieving changesets change-sets from a work item, which in turn must be found for an issue, is a costly operation. Therefore when you initially open a JIRA Jira issue page, there will be a noticeable delay before the changeset change-set is displayed. Subsequent opening of the issue page will show the changeset change-set very fast, because it has already been scanned.
Viewing
...
Change-sets in
...
Once you associate the check-in with a JIRA issue you can view details of the checked in changesets in TFS check-ins tab on JIRA issue's view screen.
...
Jira
In side panel of Jira issue page you will see "TFS Check-ins" section which contains number of check-ins associated with that issue. Click the link to open pop-up with check-ins details
In addition to checked-in files, you can also view check-in comment and any non-empty check-in notes:
Elements of each changeset associated with an issue are clickable links.
You can also view check-ins associated with all issues in the JIRA project by navigating to TFS Check-ins project tab
...
Each filename is a clickable link which leads to file content in appropriate version or file difference to previous version (depending on change type)
| Info | ||
|---|---|---|
| ||
Only users with the View Version ControlDevelopment Tools permission in JIRAJira are able to see the TFS / VSTS checkCheck-ins tabsection on the issue and projectpage. This is JIRAJira's standard way of limiting access to viewing source code to authorized users and TFS4JIRA obeys this convention. Make sure you grant this right to appropriate users. See this page for details. |