{"type":"doc","content":[{"type":"extension","attrs":{"layout":"default","extensionType":"com.atlassian.confluence.macro.core","extensionKey":"live-template","parameters":{"macroParams":{"templateType":{"value":"template"},"_parentId":{"value":"470757333"},"templateOption":{"value":"{\"label\":\"FAQ Template Cloud Ready v2\",\"value\":\"470811129\",\"templateType\":\"template\"}"},"templateTypeOption":{"value":"{\"label\":\"Confluence template/blueprint\",\"value\":\"template\"}"},"templateId":{"value":"470811129"},"excerpt":{"value":"Purpose On this KB, we will see how to associate a Salesforce Record using an API call. The Association is made using this URL: /rest/api/2/issue//properties/com.servicerocket.jira.cloud.issue.salesforce.associations This is the Jira endpoint that stores the association (entity property) There is a known limitation with Jira entity properties. This is due to a storage hard limit imposed by Atlassian Jira Cloud (maximum of 32Kb of data per issue). This roughly translates to 300 associations at most, so we are setting a recommended maximum here. More information about this limitation can be read here: Entity properties Answer Please use the following URL: /rest/api/2/issue//properties/com.servicerocket.jira.cloud.issue.salesforce.associations Replace the with your Jira Cloud base-url and with your JIRA-issue-key. The following is a sample of the JSON payload to migrate/store the associations (for 1 associations): {\n \"associations\": {\n \"\": {\n \"son\": \"Case\",\n \"viewOnly\": false,\n \"autoPush\": true,\n \"autoPull\": true\n }\n },\n \"ids\": \">\",\n \"types\": \"Case\"\n} Replace with the Salesforce Id to be associated. For multiple associations (2 associations), you can use the following JSON body: {\n \"associations\": {\n \"\": {\n \"son\": \"Case\",\n \"viewOnly\": false,\n \"autoPush\": true,\n \"autoPull\": true\n },\n \"\": {\n \"son\": \"Case\",\n \"viewOnly\": true,\n \"autoPush\": false,\n \"autoPull\": false\n }\n },\n \"ids\": \" \",\n \"types\": \"Case\"\n} For the following example we will use the Postman app https://www.postman.com/ use a PUT request (with postman) Authenticate to your Jira Cloud using API token https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/ You can create the API token in your Jira cloud instance using this URL https://id.atlassian.com/manage-profile/security/api-tokens Run a PUT request to /rest/api/2/issue//properties/com.servicerocket.jira.cloud.issue.salesforce.associations with the following payload (replace SOID with Salesforce ID) In the postman Body section add the following code: {\n \"associations\": {\n \"\": {\n \"son\": \"Case\",\n \"viewOnly\": false,\n \"autoPush\": true,\n \"autoPull\": true\n }\n },\n \"ids\": \">\",\n \"types\": \"Case\"\n} Next select JSON from the drop down menu Access the /rest/api/2/issue//properties/com.servicerocket.jira.cloud.issue.salesforce.associations on your browser and you should be seeing the associations, similar to the image bellow: One thing to note is that the associations may not appear immediately on the UI. This is because cache is at play here. The associations are stored on the property-entry, but the associations will only appear on the UI after around 20 minutes. This is normal and expected, so it may take a little while for end-users to see it on the Jira issue."},"fieldGroupKeys":{"value":"{\"8gq4t5y21n\":[\"net.customware.confluence.plugin.scaffolding__8gq4t5y21n__data_0_e5qshofg9z\"]}"}},"macroMetadata":{"macroId":{"value":"646995b7-5cf4-497c-a6f6-26bdacfebc7f"},"schemaVersion":{"value":"1"},"indexedMacroParams":{"text":"Purpose On this KB, we will see how to associate a Salesforce Record using an API call. The Association is made using this URL: /rest/api/2/issue//properties/com.servicerocket.jira.cloud.issue.salesforce.associations This is the Jira endpoint that stores the association (entity property) There is a known limitation with Jira entity properties. This is due to a storage hard limit imposed by Atlassian Jira Cloud (maximum of 32Kb of data per issue). This roughly translates to 300 associations at most, so we are setting a recommended maximum here. More information about this limitation can be read here: Entity properties Answer Please use the following URL: /rest/api/2/issue//properties/com.servicerocket.jira.cloud.issue.salesforce.associations Replace the with your Jira Cloud base-url and with your JIRA-issue-key. The following is a sample of the JSON payload to migrate/store the associations (for 1 associations): {\n \"associations\": {\n \"\": {\n \"son\": \"Case\",\n \"viewOnly\": false,\n \"autoPush\": true,\n \"autoPull\": true\n }\n },\n \"ids\": \">\",\n \"types\": \"Case\"\n} Replace with the Salesforce Id to be associated. For multiple associations (2 associations), you can use the following JSON body: {\n \"associations\": {\n \"\": {\n \"son\": \"Case\",\n \"viewOnly\": false,\n \"autoPush\": true,\n \"autoPull\": true\n },\n \"\": {\n \"son\": \"Case\",\n \"viewOnly\": true,\n \"autoPush\": false,\n \"autoPull\": false\n }\n },\n \"ids\": \" \",\n \"types\": \"Case\"\n} For the following example we will use the Postman app https://www.postman.com/ use a PUT request (with postman) Authenticate to your Jira Cloud using API token https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/ You can create the API token in your Jira cloud instance using this URL https://id.atlassian.com/manage-profile/security/api-tokens Run a PUT request to /rest/api/2/issue//properties/com.servicerocket.jira.cloud.issue.salesforce.associations with the following payload (replace SOID with Salesforce ID) In the postman Body section add the following code: {\n \"associations\": {\n \"\": {\n \"son\": \"Case\",\n \"viewOnly\": false,\n \"autoPush\": true,\n \"autoPull\": true\n }\n },\n \"ids\": \">\",\n \"types\": \"Case\"\n} Next select JSON from the drop down menu Access the /rest/api/2/issue//properties/com.servicerocket.jira.cloud.issue.salesforce.associations on your browser and you should be seeing the associations, similar to the image bellow: One thing to note is that the associations may not appear immediately on the UI. This is because cache is at play here. The associations are stored on the property-entry, but the associations will only appear on the UI after around 20 minutes. This is normal and expected, so it may take a little while for end-users to see it on the Jira issue.","type":"text"},"placeholder":[{"type":"icon","data":{"url":"https://scaffolding.bobswift.appfire.app/assets/img/80x80/Live-Template_80x80.svg"}}],"title":"Scaffolding - Live Template"}},"localId":"e8b10bd8-58e7-4992-a866-520bd2dab189"}},{"type":"paragraph"}],"version":1}

Jira REST API association