...
TFS4JIRA Synchronizer needs to store credentials for JIRA and TFS / Azure DevOps (formerly VSTS) - every password provided is stored in an encrypted(AES) form. (since version 7.1.2)
...
| Component | Data processed/stored | Remarks | ||||||
|---|---|---|---|---|---|---|---|---|
Jira Server App
| Change set metadata : author, comment etc. | Just processed, nothing is stored. No source code is processed. | ||||||
Synchronizer
| TFS / Azure DevOps (formerly VSTS) username | For synchronisation profiles and checkins scanning connection configurations. | ||||||
| Jira username | For synchronisation profiles. | |||||||
| Mapping configurations provided by TFS4JIRA user. | Any mappings configuration, that can contain private data (e.g. users mappings) | |||||||
| Data synchronised by TFS4JIRA | Any private data that is configured, by TFS4JIRA user, to be synchronised between TFS / Azure DevOps (formerly VSTS) and Jira. | |||||||
| Change set metadata : author, comment etc. |
...
| Component | Data processed/stored | Remarks | ||||||
|---|---|---|---|---|---|---|---|---|
Jira Cloud app
| Change set metadata : author, comment etc. | Just processed, nothing is stored. No source code is processed. | ||||||
Synchronizer
| TFS / Azure DevOps (formerly VSTS) username | For synchronisation profiles and checkins scanning connection configurations. | ||||||
| Jira username | For synchronisation profiles. | |||||||
| Mapping configurations provided by TFS4JIRA user. | Any mappings configuration, that can contain private data (e.g. users mappings) | |||||||
| Data synchronised by TFS4JIRA | Any private data that is configured, by TFS4JIRA user, to be synchronised between TFS / Azure DevOps (formerly VSTS) and Jira. | |||||||
| Change set metadata : author, comment etc. | ||||||||
| Additional info for TFS4JIRA cloud users: | ||||||||
TFS4JIRA cloud backend
| Change set metadata : author, comment etc. | No data is stored, it is just passed (proxied) from the Synchronizer to Jira Cloud user browser. | ||||||
...