There are some fields in which you may need to map values in Jira to values in the remote system. Typically such fields would have pre-determined values users can select from, such as Status or Priority.
It would not make sense in most situations to map free text fields, although this can be done.
Value Mappings are case sensitive and must not include trailing white spaces.
The following is an example:
In Jira you might have the following Status options:
- In Progress
In Salesforce you might have the following Case Status options:
The Jira status field is read-only, but you can still sync from Jira to Salesforce. What this means is the Connector will have to translate the status of the Jira issue to a legitimate status in Salesforce, as "Reopened" for example has no equivalent (yet) in Salesforce. You can decide to have the following mappings that make sense:
Mapping values in Jira to values in Salesforce
The above example will be used in the steps below:
- Go to the Field Mapping Configuration Interface.
- Click the Map Values link next to the configured field mapping that you would like to enable value mappings for.
- Add each value mapping in the Map Values form and click Submit after each one.
- Each mapping will appear in the Value Mappings table and should look similar to the following image when complete.
You have to specify mappings for both directions of the synchronization, so if you configure a mapping for Jira Priority to Salesforce Priority, you will need to configure a mapping for Salesforce Priority back to Jira Priority.
The reason for this is because there are cases where the mappings are not always 1 to 1 and as such, requires uni-directional mapping configurations.
Mapping null Jira values
It is possible to map null Jira values to Salesforce values instead by entering "null" while mapping values:
In the example above, when a Jira issue description is left empty by the user, the corresponding Salesforce Case description will display "Same as Summary" when the two are synchronized.