---
title: "Configure entity and field mappings from templates"
canonical: "https://support.appfire.com/space/CSFJIRA/3664152459/Configure%20entity%20and%20field%20mappings%20from%20templates"
format: markdown
---
> Macro (aura-html)
Before any data can sync between Jira and Salesforce, the two systems need to know which entities belong together. Entity mappings define these relationships, for example, telling the Connector that a Jira task corresponds to a Salesforce case, or that a Jira epic corresponds to a Salesforce opportunity. Once you establish that relationship, Jira work items and Salesforce records can be associated and kept in sync.
From there, field mappings determine how individual fields stay current between the two systems. For example, you can map the description field in Jira to its equivalent in Salesforce.
You can also define value mappings to handle terminology differences between the two systems, such as mapping Jira's In Progress status to Salesforce's Escalated to Dev, so each team continues working with the values that make sense in their own tool.
> ✅ This page helps you configure entity mappings and fields with templates.
> ✅ If you want to configure your own mappings, go to the [Configure entity and field mappings from scratch](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/3664152584) page.
## Before you start
Make sure you have:
- Administrator rights in Jira - only administrators can set up the mappings
- Added all required Salesforce objects to be available in Jira, see more [Available Salesforce objects](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/1853653945/Configure+connection+settings#Available-Salesforce-objects).
- Created a [Binding between a project and a connection](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/1873379785).
- Understand Jira field types compatibility with Salesforce field types to properly map the fields. Visit the [Jira Field Type to Salesforce Field Type compatibility](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/1522369149) page to learn more.
## Configure mapping with templates
You can select a template with ready entity and field mappings. There are five templates you can choose from:
- **Bug escalation**:** **Tracks unresolved bugs and brings cases from Salesforce to your engineering team in Jira. Maps the Jira Bug work item type to the Salesforce Case object type.
- **Feature requests**: Sends customer feature requests from Salesforce into Jira and tracks them as they move through development in both platforms. Maps Jira Story work item type to Salesforce Case object type.
- **Deal enablement**: Connect Salesforce opportunities to Jira work items. Maps Jira Epic work item type to Salesforce Opportunity object type.
- **Deal & feature sync**:** **Brings sales, product, and engineering into one workflow. Send Salesforce opportunities and customer requests to Jira, so every team stays aligned and always up to date. Maps Jira Epic work item type to Salesforce Opportunity object type, Jira Story to Salesforce Case, and Jira Bug to Salesforce Case.
- **Support requests**: Converts customer-reported issues into Jira Service Management (JSM) incidents or change requests. The template maps Jira (System) Incident and (System) Change work item types to Salesforce Case object type. The template works only with JSM Premium.
For more details, see [Mapping templates reference](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/3710386504).
1. Select **Apps** from the left sidebar in Jira.
2. Next to *Connector for Salesforce,* click **Menu** () > **App settings**.
2. Under *Connector for Salesforce*, click **Bindings**.
3. Click **Use template** to select the template you want. For example, **Bug escalation**.
The *Entity mapping *step* *opens, and the Jira work item bug type is already mapped to the Salesforce Case object type.
4. (Optional) If you want to add more entity mappings, select the Jira work item type and the corresponding Salesforce object type, and click **Add entity mapping.**
5. Select the **Bug -> Case **entity mapping to open its field mapping.
The *Field mappings* define how individual fields of items and objects interact. For the Bug -> Case entity mapping, the following fields are mapped:
| **Jira field** | **Sync direction** | **Salesforce field** |
| --- | --- | --- |
| Summary | ← → Bidirectional | Subject |
| Status | ← → Bidirectional | Status |
| Priority | ← → Bidirectional | Priority |
| Description | ← → Bidirectional | Description |
5. (Optional) If you want to add more field mappings, select the **Jira field** that matches the corresponding **Salesforce field**,** **and** **click **Add field mapping**.
Make sure the fields you map are compatible. To learn more, see [Jira Field Type to Salesforce Field Type compatibility](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/1522369149).
6. You can customize the **Sync direction** (inbound or outbound) by clicking the arrow buttons.
7. Click the **Menu** () icon next to **Priority -> Priority **field mapping and select **Configure** to open its value mapping.
The *Value mappings* define how to handle field values.
1. Set default value - decide how to handle field values not covered by the mapping. To learn more, see the [Set default value](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/3664152584/Configure+entity+and+field+mappings+from+scratch#3.-Set-default-value) section.
2. (Optional) Configure value mappings - you can also define specific value mappings to match Jira and Salesforce field values. To learn more, see the [Configure value mappings](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/3664152584/Configure+entity+and+field+mappings+from+scratch#4.-Configure-value-mappings) section.
8. Click **Next**.
Using the Bug escalation template, the Jira work item type *Bug* maps to the Salesforce *case* object type. Within this mapping, four fields sync bidirectionally between the two systems: summary to subject, status to status, priority to priority, and description to description. The priority field mapping is further configured with value mappings, so priority values stay aligned between Jira and Salesforce. With this in place, teams can track and update bugs reported as Salesforce cases in Jira, keeping both teams in sync.
## Next
- [Associate Salesforce records from Jira](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/3663725288)
- If you want to configure your custom mappings, go to the [Configure entity and field mappings from scratch](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/3664152584) page.
- [Mapping templates reference](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/3710386504)
##