Entity Mappings

Entity Mappings

An entity mapping defines the relationship between a Jira issue type and a Salesforce object type. It is the foundational rule that tells the connector: when a Jira issue of type X is linked to a Salesforce record, that record must be a Y.

A binding can have multiple entity mappings — one for each issue type you want to sync. For example:

  • Bug → Case

  • Story → Lead

  • Task → Contact

Supported Salesforce Objects

In V1, entity mappings support four Salesforce object types:

Salesforce Object

Typical Use

Case

Support tickets, incidents, escalations

Lead

Unqualified prospects or inbound enquiries

Contact

Known individuals at a customer account

Opportunity

Active sales deals

Custom objects are planned for V2.

Adding an Entity Mapping

  1. Open the binding editor from the Bindings tab.

  2. In the Entity & Field Mapping tab, click Add Entity Mapping.

  3. Select a Jira Issue Type from the dropdown (populated from your project's issue types).

  4. Select a Salesforce Object — Case, Lead, Contact, or Opportunity.

  5. Click Add.

Entity mapping configuration form showing issue type and object selectors

Entity mapping selector with Jira issue type and Salesforce object dropdowns

The entity mapping appears in the list. Each entity mapping has its own field mappings and value mappings configured separately.

Entity mappings list with Bug to Case mapping

Entity mappings list showing Bug → Case mapping with Configure Fields link

Editing and Removing Mappings

Click Configure Fields next to any entity mapping to open its Field Mappings drawer. To remove an entity mapping, click the delete icon — this also removes all field mappings and value mappings inside it.

How the Connector Uses Entity Mappings at Runtime

When a user links a Salesforce record to a Jira issue, the search modal filters by the Salesforce object types configured for that issue type's entity mapping. If no entity mapping exists for the current issue type, the Link Salesforce Record button is not shown.

When the auto-push trigger fires on an issue update, it looks up the entity mapping for the issue's type to determine which field mappings to apply before writing to Salesforce.