How can I get remote ticket key from Jira in salesforce field when exalate remote is created
Is it possible to have the Jira ticket number directly when creating the remote replica?
Indeed, we have a “Jira id” Field in which we want to put the Jira “Ticket key” value from the first outgoing on the Saleforce side.
Currently, we have the ticket key information on the Exalate component from the creation; Is it possible to put “Jira id” in a field as soon as the remote ticket exists?
To achieve this, you can customize the Exalate scripting on your Salesforce side. When you synchronize between Jira and Salesforce, you can transfer the Jira issue key to a Salesforce field by configuring the mappings.
Here’s a high-level overview of what you need to do:
Outgoing Sync on Jira Side:
Ensure that the Jira issue key is being sent over to Salesforce. This is usually the default behavior.
Incoming Sync on Salesforce Side:
In the incoming sync script on Salesforce, you need to map the Jira issue key to the Salesforce field where you want to store it.
Here’s an example of how you might modify the Salesforce incoming sync script to achieve this:
issue {
// ... other mappings
customFields.JiraId = replica.key
}
In this script, replace customFields.JiraId with the actual field name you have in Salesforce to store the Jira issue key.
For detailed instructions and more customization options, you can check the Exalate documentation for Salesforce: Exalate for Salesforce
This documentation will guide you through setting up and customizing the synchronization scripts for your specific needs.