Create a two way workflow between Jira issues and Salesforce Manufacturing request

Owned by Mark Kleinsmith
Last updated: May 06, 2024 by Jeff Gleeson
3 min read

As a Manufacturing Manager, you'll often need to have access to the inventory management team to request for resupply of stocks. When you are working on Salesforce and the inventory management team is working on Jira, you'll want a seamless workflow between these 2 divisions.

This use case shows you how to build a bidirectional workflow between Salesforce and Jira using Connector for Salesforce & Jira.

Ingredients

You will need the following installed on your Jira environment. This works for both Jira Cloud and Jira Server.

You will need some basic understanding of the following Jira features:

Complete scenario

The Teams:

  1. The team that resides on Salesforce is the team that is in charge of receiving manufacturing requests.

  2. The team that resides on Jira is the team that is working on stock and inventory management.

The Scenario:

  1. A customer reaches out to the organization seeking to manufacture a custom door frame. The team in Salesforce receive the request from the customer.

  2. The team in Salesforce raised a case that is synced with Jira issue to request for resupply of inventory.

  3. The team in Jira will track the requested items and update their inventory in Google Sheets.

  4. The Jira team can communicate with the Manufacturing team in Salesforce through the synced Jira issue.

Building this use case

⚙️ Part 1 Setup Salesforce

  1. We will be using the Case object. To make things easier across the teams that use Salesforce, we will create Record Type in Salesforce and label it as Supply Chain.

  2. Navigate to Setup > Object Manager > Case > Record Types.

  3. Add a new Record Type: Supply Chain.

  4. Having 2 Record Types allow you to create cases with different templates, similar to Issue Types in Jira.

  5. We’ve configured the Supply Chain record type to have fields that are specifically for the Manufacturing Team, such as: Item Request #1 and Item Request #1 Amount.

  6. We’ve also created Field Dependencies for Item Family and Item Request. This will allow Item Request field to have different values depending on the value defined in the Item Family field.

⚙️ Part 2 Setup Jira

  1. We will need to create the counterpart fields that we’ve done for the Salesforce. In Jira, we can use Select List (Cascading field) type for the Dependent Fields we’ve created in Salesforce.

  2. Once all of the custom fields have been created on both platforms, you can map these fields in the Bindings.

  3. 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. Thanks to the new release for SFJC, we can now map cascading fields:  Mapping Cascading Fields - Video Demonstration

⚙️ Part 3 Automation for Jira 

In this particular use-case, we didn't use any Automation for Jira. However, if you wish to do so, you can refer to this link; How to enable status transition from Salesforce to Jira via Automation for Jira to setup your Automation to best-fit your scenario.