| templateType | template |
|---|
| templateOption | {"label":"FAQ Template Cloud Ready v2","value":"470811129","templateType":"template"} |
|---|
| templateTypeOption | {"label":"Confluence template/blueprint","value":"template"} |
|---|
| templateId | 470811129 |
|---|
| excerpt | Purpose By default, you can send a Jira key to a text field which is overwritten when you have multiple associations. This guide will explain how to add multiple Jira Keys to a Salesforce rich text field (Multiple Jira keys) using Salesforce Flow . Known limitations: By unlinking or removing an association, the Jira key will not be removed from the multiple Jira key field. This needs to be done manually. The Salesforce Flow only works when creating Jira issues from Salesforce. If you create a Salesforce record from Jira, the Salesforce Flow will not trigger. These type of requests are out of support scope. We have tested this solution in our staging environment and we encourage you to test this solution in a sandbox environment before introducing it to your production environment. Salesforce Prerequisite: Jira key field (text). Multiple Jira keys (rich text). Case object. Salesforce Flow. Answer Salesforce General Configuration In Salesforce, create a text field named "Jira Key". Set the character length of a 255 characters. Create a rich text field named "Multiple Jira Key". Set the maximum field length of 32000. Set the V isible Lines value based on your use case. In Jira, create a mapping for the Key field (Jira) to the Jira Key field (Salesforce). Salesforce Flow Configuration Create a Salesforce Flow rule similar to the image below: Next, create an Update Record similar to the image below: Set the following in the Configure Trigger section in the Salesforce Flow configuration: Trigger the Flow When: A record is created or updated. Next, set the following in the Set Entry Conditions section: Follow the configuration for the When to run the Flow for Updated Records and Optimize the Flow for : Set the following conditions: JIRA_Key__c is Null = False (To get the key when you create a Salesforce record from Jira.) JIRA_Key__c is changed = True (To halt the rule from running in a loop and to only execute when the Jira key changes.) In the Edit Formula section set the following. This will append the Jira Key to the Multiple Jira Key: {!$Record.Multiple_Jira_Keys__c} &' '& {!$Record.JIRA_Key__c} Salesforce Updates Record Configuration Set the following in the Jira key append section in the Updates Record configuration: How to Find Records to Update and Set Their Values: Specify conditions to identify records, and set fields individually. Next, set the following in the Set Entry Conditions section: The Value field in the image above is an example, change this to the object that you want to configure to. You can debug the setup by going to Case RecordID > Activate > Save . The Multiple Jira Keys field will have this format, ex: "CSF-347 CSF-348 CSF-300". Once the configuration is complete, Jira key field changes with a new value (from a new Jira issue created from Salesforce or any new associations). The multiple Jira key will take that new value from the Jira key field. Notes Once the Salesforce Flow is created, you will be able to create a report in Salesforce based on the Jira keys. This enables you to see all the associated Jira keys to a Case Record. More information about the report creation in Salesforce can be read here: Salesforce Reporting on Jira Issue Key |
|---|
| fieldGroupKeys | {"8gq4t5y21n":["net.customware.confluence.plugin.scaffolding__8gq4t5y21n__data_0_zvf3jvc10ve8mq548zpw"]} |
|---|
|