As a services manager you receive requests often from different customers with different needs. Once you prepare a statement of work(SOW), you would need to access the legal team for final contract/proposal preparation. You'll now want to have a seamless workflow between the services team (working on Jira) and the legal team (who are working on Salesforce).
This use case shows you how to build a bidirectional workflow between Salesforce and Jira using Connector for Salesforce & Jira. Together with Jira's built-in functions like custom fields, workflows, post-functions, and Automation for Jira.
The team that resides on Salesforce is the Legal team.
The team that resides on Jira is the support and services team
A customer reaches out to the organization's support team seeking their assistance.
Support/Services then creates an internal Jira ticket for their request of a SOW/pre-contract.
The created Jira ticket is synced with a Legal Case in Salesforce.
The Legal team will find new Case created in Salesforce and work on them.
The Legal team updates the object in Salesforce once they have provided what they need and it'll automatically get updated in Jira.
The Services team that is working with the customer can now update the customer with the information that they need.
Building this use case
⚙️ Part 1 Setup Salesforce
We will be using the Case object. To make things easier across the teams that use Salesforce, we will be creating a Record Type in Salesforce and label it as Legal Case
Navigate to Setup > Object Manager > Case > Record Types
Add a new Record Type: Legal Case
This will then show up on the object as Case Record Type to differentiate what type of Case is it:
From the Case Settings screen shown in step 2, you can also navigate to Fields & Relationships to add new fields, such as Contract Type, Contract Due Date, and so on.
You can add a field namely Pending for Legal? to act as a middleman. It is a Picklist field in Salesforce and it only has “Yes” and “No” options. We’ll touch more on this later in the Jira’s configuration section.
⚙️ Part 2 Setup Jira
There are a few things that need to be configured in Jira:
You will need to create the counterpart fields that you have created for in Salesforce. For example, if you have created a field for Contract Type in Salesforce, you need to do the same in Jira by creating a Select List (Single Choice) field type and have the same values for the field.
As mentioned in step 6 on the Salesforce configuration part, we created a field named “Pending for Legal?”, now we are creating the counterpart for it in Jira as well.
Once all of the custom fields have been created on both platforms, you can map these fields in the Bindings.
To do that, navigate to Apps > Salesforce > Bindings, click on Mapping for the project you’re linking it to, click Mappings for the issue type that you want to map these fields:
⚙️ Part 3 Setup Workflow Status/Post-function
Create 2 statuses in Jira by navigating to Settings > Issues > Statuses. We created 2 statuses: Waiting for Legal and Waiting for Jira Team
We added these 2 statuses to the workflow of the project:
Click on the transition to the Waiting for Legal status, and a pop-up will appear on the right as shown in the screenshot above.
Click on Post Functions
We added 2 Post Functions: Update Issue Custom Field and Push to Salesforce
The Update Issue Custom Field is to update the Pending for Legal? field to Yes whenever this transition is made
The Push to Salesforce is to automatically push the mapped fields to Salesforce
⚙️ Part 4 Automation for Jira
We need to add an automation to enable the ability to transition the issue in Jira from Salesforce.
Navigate to Settings > System > Automation Rule
Click Create Rule on the top right
Select the Field Value Changed trigger and search for Pending for Legal? field. Click Save.
- Select New Condition.
- Select User condition and select User who triggered the event for the User field, Is for the Check to perform field, Salesforce & Jira Cloud Connector for the Criteria field:
- After saving, click New action:
- Select Transition issue:
- Choose Waiting for Jira Team for the Destination Status. Click Save.
- Click Turn it on