---
title: "TFS / Azure DevOps (formerly VSTS) check-ins synchronization"
canonical: "https://support.appfire.com/space/TSH/1800668823/TFS%20%2F%20Azure%20DevOps%20(formerly%20VSTS)%20check-ins%20synchronization"
format: markdown
---
## 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 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.

![image](media://612aaac0-a00b-4bca-afff-057e28d5791c)

This is the standard 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 issue by typing an issue key as a part of any [check-in note](http://msdn.microsoft.com/en-us/library/ms181281%28v=vs.80%29.aspx) 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 integration policy.

![image](media://584f409d-08bd-4da6-8dc3-8459f3207069)

### **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 issues synchronization](https://appfire.atlassian.net/wiki/spaces/TSH/pages/1800799057) and (in case of Jira Cloud environment) exposed it to web requests from the Internet (see [Settings for JIRA Cloud](https://appfire.atlassian.net/wiki/spaces/TSH/pages/1800209916)), associating check-ins with 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 change-set.

![image](media://eec25d55-9d78-4436-9dfc-1889bd0e8dcf)

Scanning of change-sets associated with a Jira issue synchronized to a work item is done "lazily" for performance reason, because retrieving 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 issue page, there will be a noticeable delay before the change-set is displayed. Subsequent opening of the issue page will show the change-set very fast, because it has already been scanned.

## Viewing Change-sets in 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

![image](media://46e4395c-3381-47f3-93a3-cdabc7c698f3)

![image](media://9c9a907b-9caf-4bfc-96f7-7de8ec566601)


In addition to checked-in files, you can also view check-in comment and any non-empty check-in notes:

![image](media://ee768638-4034-4b10-9ec9-b28b6fd250da)

Each filename is a clickable link which leads to file content in appropriate version or file difference to previous version (depending on change type)

![image](media://b3391629-bc2a-4d06-99ea-544c8d9c8156)


> ℹ️ ### Note
> ℹ️ 
> ℹ️ Only users with the **View Development Tools** permission in Jira are able to see the TFS Check-ins section on the issue page. This is Jira'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](https://confluence.atlassian.com/adminjiraserver070/managing-project-permissions-749382918.html) for details.