Field Mappings
Field mappings define which Jira fields sync to which Salesforce fields — and in which direction. They live inside an entity mapping and are applied every time data is pushed or pulled between the two systems.
Sync Directions
Each field mapping has a direction:
Direction | Meaning |
|---|
Jira → Salesforce | When data is pushed, this Jira field's value writes to the mapped Salesforce field. Pull operations ignore this mapping. |
Salesforce → Jira | When data is pulled, this Salesforce field's value writes to the mapped Jira field. Push operations ignore this mapping. |
Bidirectional | Both directions apply — push uses the Jira value, pull uses the Salesforce value. |
Configuring Field Mappings
In the binding editor, click Configure Fields next to an entity mapping.
The field mapping drawer opens. On the left, Jira fields are listed (populated from the Jira issue schema). On the right, Salesforce fields are listed (fetched live from your Connected App's object describe endpoint).
Click Add Mapping. Select:
The Jira Field (e.g. Summary)
The Salesforce Field (e.g. Subject)
The Direction (Jira→SF, SF→Jira, or Bidirectional)
Click Save Mappings.
Field mapping drawer with Jira and Salesforce field selectors
Direction selector showing Jira→SF, SF→Jira, and Bidirectional options
Common Mapping Examples
Jira Field | Salesforce Field | Direction | Notes |
|---|
Summary | Subject | Jira→SF | Issue title drives Case subject |
Status | Status | Bidirectional | Syncs in both directions |
Priority | Priority | Jira→SF | Jira priority maps to SF priority |
Description | Description | Jira→SF | Rich text is stripped to plain text |
Saved field mappings list showing three active mappings with directions
What Happens to Unmapped Fields
Fields without a mapping are not touched during sync. If you push a Jira issue and a Salesforce field has no mapping, that field stays as-is in Salesforce. This is intentional — unmapped fields preserve any data that Salesforce owns independently.
Field Type Compatibility
Salesforce and Jira use different field types. The connector passes values as-is where types match. Where they differ — for example, mapping a Jira status string to a Salesforce picklist — use Value Mappings to translate specific values.