---
title: "Check-ins with Jira Cloud and Azure DevOps Cloud"
canonical: "https://support.appfire.com/space/TSH/1800243060/Check-ins%20with%20Jira%20Cloud%20and%20Azure%20DevOps%20Cloud"
format: markdown
---
# Components and Deployment

![image](media://7dd9085b-5a26-4dfd-8844-188e2e107e39)

# Interactions

![image](media://fd9707c0-789e-445b-86f7-7803b50f2068)

# Encryption

`TFS4JIRA Synchronizer` and `TFS4JIRA OnDemand `communicate over HTTPS, in addition the payload is encrypted with a tenant - specific key, using standard .NET implementation of the Advanced Encryption Standard (AES) algorithm.

# Synchronizer Endpoints

In order for the check-ins functionality to work, the following `TFS4JIRA Synchronizer` endpoints need to be visible from the outside world, as they are used by the `TFS4JIRA OnDemand` application:

- GetIssueAssociatedChangesets
- GetIssueChangesets
- Rescan
- TestConnection

## GetIssueAssociatedChangesets

Retrieves check-ins associated with a Jira issue via TFS commit Note, as described in [Associating using a check-in note](https://appfire.atlassian.net/wiki/spaces/TSH/pages/1800668823/TFS+Azure+DevOps+formerly+VSTS+check-ins+synchronization#Associating-using-a-check-in-note).  
**Input**: Jira url and issue key(s).  
**Output**: Check-ins.

## GetIssueChangesets

Retrieves check-ins associated with a Jira issue via TFS commit message text, as described [Associating using a check-in comment](https://appfire.atlassian.net/wiki/spaces/TSH/pages/1800668823/TFS+Azure+DevOps+formerly+VSTS+check-ins+synchronization#Associating-using-a-check-in-comment).  
**Input**: Jira url and issue key(s).  
**Output**: Check-ins.

## Rescan

Scans target repository one more time, in an attempt to find a missing check-in.  
**Input**: repository, change set.  
**Output**: success flag.

![image](media://ed21f052-6f6a-4807-b968-56dfcaa5dc98)

## TestConnection

Tests connection between `TFS4JIRA OnDemand` application and `TFS4JIRA Synchronizer`.  
**Input**: Jira url, sample data to verify encryption correctness (literally, “test” sting).  
**Output**: Jira url, number of repositories configured, sample data.

![image](media://3e3e88b0-373e-469a-932d-a7c519e92bb6)

# Check-ins Schema

![image](media://fb543b8a-1a12-4fa4-8492-a5f2ac113cb9)

See json schema attached