Permissions needed by TFS4JIRA Synchronizer - Cloud Native
- spg bot
- Damian Kilkowski (Inactive) (Deactivated)
Jira permissions
Project role:Â atlassian-addons-project-access must have granted the below permissions:
Permission | Required | Notes |
|---|---|---|
Add Comments |  | Only if Comments synchronization is enabled |
| Assign Issues | | Only if the Assignee field is mapped |
| Browse Projects |  | |
| Close Issues | | |
Create Attachments | | Only if Attachment synchronization is enabled |
| Create Issues | | |
Delete Issues |  | In exceptional cases due to race conditions, we may create orphan items that have to be cleaned up |
Edit Issues | | |
Modify Reporter | | Only if the Reporter field is mapped |
Resolve Issues | | |
Transition Issues | |
Azure DevOps permissions
TFS4JIRA Synchronizer connects to Azure DevOps (ADO) using the credentials provided in the synchronization profile. For the work items / issues synchronization to work, the user must have the following permissions:
Organization
| Access Level | Required | Notes |
|---|---|---|
Basic | | Only if Tags field is mapped |
Project
| User Group | Required | Notes |
|---|---|---|
Contributors | | Minimum set of permissions |
Jira permissions
TFS4JIRA Synchronizer connects to Jira Cloud using Jira's built-in mechanism for Atlassian Cloud apps. Once TFS4JIRA app is installed on your Jira Cloud instance the special permission is granted to the app to call Jira APIs, with respect to app scopes. No additional configuration is required.