...
This use case shows you how to build a bidirectional bidirectional workflow between Salesforce and Jira using Connector for Salesforce & Jira.
...
Salesforce
You will need some basic understanding on of the following Jira features:
...
We will be using the Case object. To make things easier across the teams that use Salesforce, we will be creating a create Record Type in Salesforce and label it as Supply Chain.
Navigate to Setup > Object Manager > Case > Record Types.
Add a new Record Type: Supply Chain.
Having 2 Record Types allow you to create cases with different templates, similar to Issue Types in Jira.
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.
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.
...
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.
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. Thanks to the new release for SFJC, we can now map cascading fields: Mapping Cascading Fields - Video Demonstration
⚙️ Part 3 Automation for Jira
...