Breadcrumbs

Field Mappings

Define which fields are synchronized in the Fields - Mappings tab of the configuration.

With Backbone you can map fields either bi-directional or uni-directional. Standard Jira fields as well as most custom fields are supported. You can find a full list of supported fields here.

On this page you both find the requirements to synchronize fields and two ways on how to set up fields: simple and advanced.

Requirements to Sync Fields

To synchronize fields, you need to make sure that:

  • Every field which should be edited by Backbone should be on the edit screen for this project/work type. If you want to use a transition instead, please check out the advanced setting sync.editTransition.

  • Backbone needs the "Edit Issues" permission for each project where you define incoming field mappings

Add Field Mappings

You can add fields in two ways: through a simple mapping when the name and types are the same (e.g. summary <> summary) or an advanced mapping. You can always make use of a combination of both.

Simple mapping

You can use the simple mapping to quickly add fields that have the same name and type and don’t require any further configuration. To add fields through the simple mapping, you can follow these steps:

  1. Click + Field mapping > Simple

Field-mapping-add-menu.png
  1. In the dialog, select which field(s) you want to sync by checking the box(es)

  2. On the top, choose the direction you want these fields to be synced in

  3. Click on “Create“ to add the fields to your configuration

Field-mapping-simple.png

Advanced mapping

You can use the advanced mapping to add fields that are not of the same type, need to be synced for only certain work types or need further configuration. For example:

  • Fix Version <> Affected Version

  • Select Field One <> Select Field Two

  • Reporter > Text Field

You can follow these steps to add an advanced field mapping:

  1. Click + Field mapping > Advanced

  2. Choose the fields on each side which you want to map to each other

  3. Pick the direction in the middle of the two fields

Field-mapping-advanced.png
  1. Optional: uncheck “applies for all “work types” to only specify certain work types the field should be synced on.

  2. Optional: click on “configure“ to select different mappings

  3. Click on “save“ to add the field mapping to the configuration

Edit or Delete Field Mappings

Once you’ve added your fields, they show up in the Field - Mappings tab. From here you can take different actions:

  • Edit: click on the pencil icon to open up the dialog to alter the field mapping.

  • Disable/enable: click on the eye icon to disable/enable the field mapping. This can come in handy if you want to test something or later want to add the field mapping again.

  • Delete: click on the trash icon to delete your field. You can always add it again later if needed.

Field-mapping.png

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, Backbone supports 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, please refer to the field mapping reference.

Field Name

Supported?

Affects Version/s

check mark

Assets fields

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 work item 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

Work Type

check mark (using advanced.issueTypeChangeAllowed advanced setting)

Key

check mark  (read-only)

Labels

check mark

Last Viewed

check mark  (read-only)

Linked work items

check mark

Multi-select fields

check mark

Multi-level cascading select

check mark  

Original Estimate

check mark

Parent

check mark (only if the parent work item 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)