...
| 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 .is stored in DB | ||||||
| Jira username | For synchronisation profiles .is stored in DB | |||||||
| Mapping configurations provided by TFS4JIRA user. | Any mappings configuration, that can contain private data (e.g. users mappings - like names and emails) is stored in DB | |||||||
| Data synchronised by TFS4JIRA | Only processed. Any private data that is configured, by TFS4JIRA user, to be synchronised between TFS / Azure DevOps (formerly VSTS) and Jira. | |||||||
| Issue key and project key of synchronized pairs along with errors that happen while synchronizing them | Stored in DB and processed | |||||||
| Change set/commit metadata : author, comment, file names etc. | Stored in DB and processed |
TFS4JIRA Cloud
In our Jira Cloud solution most of the data is processed/stored by TFS4JIRA Synchronizer component - which runs in client infrastructure.
Only data needed for Jira Cloud app are processed (proxied) trough our infrastructure. See below table, diagram and description for details.
...