How to bulk push information from Salesforce to Jira

When we add a new field in Jira and map it to a salesforce field, the information from Salesforce will not be automatically sent to the new field. To make it possible, we need to bulk push from Salesforce. However, this is not a feature out of the box. The following workaround explains how to do a bulk push from Salesforce.

 Instructions

1. Create a “string” field in jira and add it to the edit screen for the Jira Issue.

2. Create a “text” field in Salesforce and add it to the Case layout. Help And Training Community

3. Map both fields between them.

4. Set our auto-push trigger in your instance. More information can be found here Configuring Automatic Pull from Salesforce.

   trigger CaseUpdatedTrigger on Case (after update) { JCFS.API.pushUpdatesToJira(); }

5. In Salesforce, make a mass update on the created field (add a value) to trigger the APEX trigger.

6. Follow the steps below for the mass update:

   1. Click on Cases at the top of Salesforce

   2. Select “All Open Cases” List Views.

      Open

      

   3. If you have Record Types on your cases, follow the steps below; if not go to point d.

      1. Click on the filter button > Add Filter > Field: Case Record Type - Operator: equals - Value: Select one of the Request Types. > Click on Save

         Open

         

   4. Click on the “List View Control” Button > Select Fields to Display > Select the created SF field on step 2. > Click on Save.

   5. Select a max of 50 cases by clicking on the Checkbox at the beginning of the list.

      1. Please note that Salesforce Future methods are subject to asynchronous execution limits, which include a limit of 50 calls per transaction and a maximum timeout of 60 seconds.

   6. In the first case of the list, click on the Created field in Step 2 and edit it with any value. You should see a checkbox asking you to update the 50 selected items. Check the box and click Apply.
      
      

   7. This will update all the selected cases, thus activating the trigger implemented in point 4 and causing a bulk push.

   8. Repeat steps b to f for all cases that need to be updated.