- 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
- Synchronize with 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
- Custom Field Mapping Error
- 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 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
- Use the Java API
- Synchronization behavior
- Data Encryption
- Handling Personal Data
Field mappings let you define which fields are mapped between synchronized issues.
Are you on the right help page?
If you connect Jiras...
...via HTTP(S) (centralized configuration), check out this page instead.
...via email or file exchange (distributed configuration), you're in the right place.
Like Issue Type Mappings, they can either be mapped bi-directionally (master <> slave) or uni-directionally (master > slave or slave > master). However, field mappings can only be created on the master side.
This guide will explain how to work with field mappings on both the master and slave sides.
Field mappings – master
On the master side, you can create all the new field mappings which you'd like to have. You can also select the direction of the synchronization using the arrow dropdown menu in the middle of the form. If you leave the ‘All Issue Types’ box checked, this field mapping will be activated on issue syncs of all types. By unchecking the box, you can choose to have this field type mapping activated for only selected issue types. When creating field mappings, you cannot map a field directly to a certain field on the partner side. This is because each partner controls their own side of the synchronization. You must assign the mapping a message alias, which is a label that determines how it is presented to your synchronization partner. The message should make it clear to the synchronization partner which field they should map it to on their side.
Field mappings – slave
On the slave side, you can configure the new mappings by mapping them to the relevant fields on your side of the configuration. The mappings should come with a message alias that clarifies which field you should map it to on your side. In this case, the message alias is 'description' – so it is clear that you should map it to the 'description' field. Contact your synchronization partner If it is unclear what field you should assign the mapping to.
Field mappings cannot be created on the slave side – the slave can only configure field mappings sent to them from the master side.