- Bidirectional synchronization
- Unidirectional synchronization
- Synchronize Jira Server with Jira Cloud
- Synchronize one project with multiple others
- Synchronize a private with a public project
- Synchronize projects behind firewalls
- Synchronize without installing
- Synchronize with changing Jiras
- Migrate Jira projects
- JIRA Service Desk
- Analyze and fix errors
- Trigger a resync
- Increase the JIRA logging level
Fix common problems
General problem situations
- 411 - Length required
- All fields have English names although Jira is in a different language
- Authentication with an external Jira fails
- Exception: ServiceLocatorImpl has been shut down
- Sync info panel displays wrong synchronization name, and no link to partner project
- Server is not reachable - how to fix it
- Changes are not being synchronized
- Can't change the synchronization user
- Recently created issue types, fields, etc. are not available when editing configuration
Issue specific problem situations
- Admin or project admin permissions are required
- Bad gateway
- Cannot add or remove watcher
- Cannot create new issue without mapped issue type
- Cannot find transition
- Cannot find transition id
- Component(s) not valid
- Field not on the Screen
- Incoming Issue Error
- Incompatible message format
- Invalid license
- Invalid regex syntax
- Issue does not exist
- Issues must be assigned
- JIRA is offline
- Missing attachment permissions
- Missing Issue
- Missing issue type mapping
- Missing message
- Missing parent Issue error
- Missing required fields
- No create version permissions
- No permissions to view this request for JIRA Service Desk
- No project administration permissions
- Option not valid
- Outgoing Issue error
- Outgoing Send Error
- Priority not valid
- Resolution cannot be chosen
- Sprint does not exist
- Template error
- The requested board cannot be viewed
- User does not exist
- User not assignable
- Version(s) not valid
- Workflow operation not valid
- General problem situations
- Field mapping reference
- REST API
- Synchronization behavior
- Data Encryption
Define whether comments are synchronized between instances.
Comments will be added or edited by the synchronization user. Therefore changes by different users in the partner project will appear as synchronization user changes.
If you like to have more details about the actual author and timepoint of the comment, you can activate the enrichment where you can specify a velocity template which will generate the comment content. The following template variables are available:
The actual content of the comment.
|The display name of the user who wrote the comment.|
|The email address of the user who wrote the comment.|
|The time when this comment has been added|
|The display name of the user who edited the comment.|
|The email address of the user who edited the comment.|
|The time when this comment has been edited.|
The visibility of a Jira Servicedesk comment, either public or internal. Please use this option only in JSD scenarios.
|The timezone in readable form (helpful when your partner project uses a different time zone than you).|
- If a comment has been added in project A and later deleted in project A, the comment would also be deleted in project B.
- If a comment has been added in project A and later deleted in project B, the comment will not be deleted in project A. If this comment is then edited in project A, it will be recreated in project B.
- Whenever comments are edited in the project where they have been created originally, the corresponding comments in the other project will be updated (overwritten).
Only synchronize certain comments
It's possible to configure JIRA so that only certain comments you make are synchronized to the partner instance.
- Create a group, e.g. 'Internal', and assign all users of the internal JIRA to it except the synchronization user.
- Switch your JIRA's comment visibility so that Groups & Project Roles are allowed.
- For every comment you only want to see internally, restrict it to the group 'Internal'.
- For every comment that should be public, no restriction should be applied.
With this configuration in place, the synchronization user can not see the internal comments anymore and will not synchronize them to the public JIRA.