Skip to main content
Skip table of contents

Field Mappings (email/file exchange)

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) (server/data center, cloud, local), check out this page instead.
... via email or file exchange (server/data center behind a firewall), 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.

Please note that every field which should be edited by Backbone should be on the edit screen for this project and issue type combination. If you don't want this behavior, have a look at the advanced setting sync.editTransition.

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 'summary' – so it is clear that you should map it to the 'summary' 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.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.