Skip to main content
Skip table of contents

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

  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

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

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

(tick)

Assignee

(tick)

Attachment

(tick)

Comment

(tick)

Component/s

(tick)

Created

(tick) (read-only)

Creator

(tick) (read-only)

Customer Request Type

(tick)

Description

(tick)

Due Date

(tick)

Environment

(tick)

Epic color

(tick)

Epic link

(tick) (only if the parent work item is part of the synchronization)

Epic name

(tick)

Epic status

(tick)

Epic theme

(tick)

Fix Version/s

(tick)

Flagged

(tick)

Images (this is not the Attachments field)

(error)

Work Type

(tick) (using advanced.issueTypeChangeAllowed advanced setting)

Key

(tick) (read-only)

Labels

(tick)

Last Viewed

(tick) (read-only)

Linked work items

(tick)

Multi-select fields

(tick)

Multi-level cascading select

(tick) 

Original Estimate

(tick)

Parent

(tick) (only if the parent work item is part of the synchronization)

Priority

(tick)

Progress

(error)

Project

(error)

Project-specific select

(tick)

Project-specific multi-select

(tick)

Remaining Estimate

(tick)

Reporter

(tick)

Resolution

(tick)

Resolved

(tick) (read-only)

Request participants

(tick) (read-only)

Satisfaction date

(tick)

Security Level

(error)

Select fields

(tick)

Single version picker

(tick)

Sprint

(tick)

Status

(tick) (read-only)

Story points

(tick)

Sub-Tasks

(tick)

Summary

(tick)

Time Spent

(tick) (read-only)

Updated

(tick) (read-only)

Votes

(tick) (read-only)

Watchers

(tick)

Work Ratio

(error)

Worklogs

(tick)

∑ Original Estimate

(tick) (read-only)

∑ Progress

(error)

∑ Remaining Estimate

(tick) (read-only)

∑ Time Spent

(tick) (read-only)


JavaScript errors detected

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

If this problem persists, please contact our support.