Manual
Field Mappings
Roman Serazhiev Last update: Jan 3, 2019
Define which fields are synchronized between instances.
Fields can be either mapped either bi-directional or uni-directional if a field value mapping 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 value mapping (transformation). Please refer to Field Reference for detailed information on which system fields are supported so far. Custom fields are also supported.
Field Value 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 value 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.
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.
Info
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:
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.
After you have configured the mappings, click the create button and they will be configured on your synchronization.
Note
With the suggestions 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 the Suggestions 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. If you miss support for a certain field, please let us know via the support button.
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 |  |
| Assignee | |
| Attachment | |
| Comment | |
| Component/s | |
| Created | (read-only) |
| Creator | (read-only) |
| Customer Request Type |  |
| Description | |
| Due Date | |
| Environment | |
| Epic color | |
| Epic link | |
| Epic name | |
| Epic status | |
| Epic theme | |
| Fix Version/s | |
| Flagged | |
| Images (this is not the Attachments field) |  |
| IssueType | (using advanced.issueTypeChangeAllowed advanced setting) |
| Key (IssueKey) |
|
| Labels | |
| Last Viewed | (read-only) |
| Linked Issues | |
| Log Work | |
| Multi-select fields | |
| Multi-level cascading select | (read-only) |
| Original Estimate | |
| Priority | |
| Progress | |
| Project | |
| Project-specific select | |
| Project-specific multi-select | |
| Remaining Estimate | |
| Reporter | |
| Resolution | |
| Resolved | (read-only) |
| Request participants | (read-only) |
| Satisfaction date | |
| Security Level | |
| Select fields | |
| Single version picker | (read-only) |
| Sprint | |
| Status | (read-only) |
| Story points | |
| Sub-Tasks | |
| Summary | |
| Time Spent | (read-only) |
| Time Tracking | |
| Updated | (read-only) |
| Votes | (read-only) |
| Watchers | |
| Work Ratio | |
| ∑ Original Estimate | (read-only) |
| ∑ Progress | |
| ∑ Remaining Estimate | (read-only) |
| ∑ Time Spent | (read-only) |