Value Mappings

Value mappings translate specific field values between Jira and Salesforce. Where Jira calls a status "In Progress" and Salesforce calls the equivalent "Working", a value mapping bridges the gap so both systems stay consistent.

Value mappings apply on top of field mappings — they are configured per entity mapping, per field pair.

When You Need Value Mappings

Value mappings are most useful for:

• Status fields — Jira statuses (To Do, In Progress, Done) rarely match Salesforce picklist values (New, Working, Closed)

• Priority fields — Jira's Highest/High/Medium/Low/Lowest vs. Salesforce's P1/P2/P3/P4

• Type/category fields — any picklist where the two systems use different labels for the same concept

Configuring Value Mappings

1. In the binding editor, click Configure Fields next to an entity mapping.

2. Next to a field mapping row, click Value Mappings.

3. The value mapping modal opens. On the left, your Jira field's values are listed. On the right, enter the corresponding Salesforce value for each Jira value.

4. Click Save.

Value mapping modal showing Jira status values with Salesforce equivalents

Completed value mapping table — In Progress → Working, Done → Closed

How Value Mappings Are Applied

When pushing from Jira to Salesforce:

1. The connector reads the Jira field value for the issue.

2. If a value mapping exists for that value, it substitutes the mapped Salesforce value.

3. The mapped value is sent to Salesforce.

When pulling from Salesforce to Jira, the reverse mapping is applied — the Salesforce value is translated back to the Jira value before writing to the issue field.

Values Without a Mapping

If a Jira value has no mapping defined, the raw Jira value is sent to Salesforce as-is. If Salesforce rejects it (for example, because it is not a valid picklist option), the push will fail with a Salesforce API error visible in the sync status.