Breadcrumbs

Field Mappings

Define which fields are synchronized between instances.


Are you on the right help page?

If you connect Jiras...
...via HTTP(S) (server/data center, cloud, local), you're in the right place.
...via email or file exchange (server/data center behind a firewall), check out this page instead.


Fields can be mapped either bi-directional or uni-directional if a Field Mappings is available. In general you can map fields of the same type to each other e.g. Summary to Summary. Other mappings might require a specific field mapping (transformation). Please refer to Field Mapping References for detailed information on which system fields are supported so far. The standard custom fields are also supported.

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-mapping-advanced.png

Field Mapping 

If fields can be mapped to each other without further configuration you will be able to save in the first step of the create field mapping wizard. If not or if you want to customize the proposed mapping the next steps of the wizard will allow you to define the field mappings. For a select customfield you can for example map its single options there. Depending on your chosen directions, you will see one or both screens below.

Field-mapping-advanced-configure-A-to-B.png
Field-mapping-advanced-configure-B-to-A.png

After you've created a field mapping, you can see it in the list of field mappings. It is also possible to delete or edit an existing field mapping from here.

Field-mapping.png

Please note that you need the "Edit issues" permission for each project where you define incoming field mappings.

Speed It up With Simple Mappings

Speed things up with the simple mappings feature by adding multiple Field Mappings at the same time using a menu with checkboxes.

To open the simple mappings menu, click +Field mapping > Simple:

Field-mapping-add-menu.png

Now, a menu will appear where you can map all of a project's Fields with the corresponding Fields of the other project. You can select which Fields you wish to map using the checkboxes, and you can choose the direction of the synchronization using the dropdown list at the top of the screen.

Field-mapping-simple.png

After you have configured the mappings, click the create button and they will be configured on your synchronization.

With the simple mappings menu, you can only map a project's Fields with the same type of the other project (Description<>Description, Assignee<>Assignee etc.). If you want to map different Issue Types (e.g. Description<>Assignee) to one another, you have to do it manually.

Each time you use this tool, you can only add synchronizations going in the same direction. If you want to add synchronizations going in more than one different direction, you have to use the tool multiple times.

Field Reference 

System Fields

This list shows which system fields are supported by Backbone. Read-only indicates that the field can only be synchronized in one direction. If you miss support for a certain field, please let us know via the support button.

In general, we support three different types of field mappings: PassthroughCorrelation and To Text. You can read more in the article about Common Field Mapping Types. For detailed information on how to synchronize some of the more complex mappings, refer to the field mapping reference.

Field Name

Supported?

Affects Version/s

check mark

Assignee

check mark

Attachment

check mark

Comment

check mark

Component/s

check mark

Created

check mark (read-only)

Creator

check mark  (read-only)

Customer Request Type

check mark

Description

check mark

Due Date

check mark

Environment

check mark

Epic color

check mark

Epic link

check mark (only if the parent issue is part of the synchronization)

Epic name

check mark

Epic status

check mark

Epic theme

check mark

Fix Version/s

check mark

Flagged

check mark

Images (this is not the Attachments field)

cross mark

IssueType

check mark (using advanced.issueTypeChangeAllowed advanced setting)

Key (IssueKey)

check mark  (read-only)

Labels

check mark

Last Viewed

check mark  (read-only)

Linked Issues

check mark

Multi-select fields

check mark

Multi-level cascading select

check mark  

Original Estimate

check mark

Parent

check mark (only if the parent issue is part of the synchronization)

Priority

check mark

Progress

cross mark

Project

cross mark

Project-specific select

check mark

Project-specific multi-select

check mark

Remaining Estimate

check mark

Reporter

check mark

Resolution

check mark

Resolved

check mark  (read-only)

Request participants

check mark  (read-only)

Satisfaction date

check mark

Security Level

cross mark

Select fields

check mark

Single version picker

check mark

Sprint

check mark

Status

check mark  (read-only)

Story points

check mark

Sub-Tasks

check mark

Summary

check mark

Time Spent

check mark  (read-only)

Updated

check mark  (read-only)

Votes

check mark (read-only)

Watchers

check mark

Work Ratio

cross mark

Worklogs

check mark

∑ Original Estimate

check mark  (read-only)

∑ Progress

cross mark

∑ Remaining Estimate

check mark  (read-only)

∑ Time Spent

check mark  (read-only)