This article instructs you on how to configure Atlassian’s Connector fo Salesforce&Jira app in JIRA in order to associate CIs and your Jira tickets.
Go to JIRA marketplace to locate the app Connector For Salesforce & Jira. Make sure to have familiarized with pricing or free trial terms before adding the app to your JIRA.
Configuration
1. In your JIRA go to Apps → Salesforce.
2. Under CONFIGURATION go to Connections. Click +Add Connection.
3. Give the connection a name → Add.
4. Locate the created connection in the list → click Authorize.
5. Select Salesforce environment (Production if you have active org) → Authorize.
6. Log in to your Salesforce instance.
If you don't have Salesforce password, log in to your Cloudaware account → Setup → Users → locate your user → Edit → check the box 'Generate new password and notify user immediately' → Save → click 'Reset Password' → OK → check your email.
Select Allow.
7. Skip the message 'Import Compact Layouts' selecting I'll do it later.
8. Locate the created connection in the list → click Configure.
9. Manage the connection:
9.1. Set up Available Salesforce Objects. Click +Add Salesforce Object.
Select the Salesforce object from the list. Click Next.
Select the relevant fields for this Salesforce object clicking +Add to save the previously selected field.
Pay attention to the primary-secondary relation. The primary field will be used for filtering.
Once all fields are added, click Next.
Add more objects if necessary. Examples of objects and fields for different clouds:
AWS | Azure | Google Cloud | |||
|---|---|---|---|---|---|
AWS Account | Account Name Account ID Roles Status: Collector Deleted | Azure Subscription | Subscription Name Subscription ID | Google Project | Google Project Name Status (Collector) |
AWS EC2 Instance | Instance Name or ID Instance ID State Name Deleted from AWS | Azure Virtual Machine | Azure Virtual Machine name VM ID Power State Deleted from Azure | Google GCE Instance | Google GCE Instance Name Google ID Status Deleted from Google |
Click Apply changes.
9.2. Configure Connection Settings: (set the following options as toggled)
Allow Modification
Allow Automatic Push
Allow Automatic Pull
9.3. Configure Default Presets: (set the following option as toggled)
Automatic Pull
Click Apply changes.
10. Create custom fields 'Object Type' and 'Object Identifier' in your JIRA.
To create a custom fields in JIRA, go to Settings (Gear icon) → Issues → select Custom fields under FIELDS (on the left) → Create custom field:
a. Select 'List (single choice)' as a field type → Next → name the field 'Object Type' → in 'Options' select every field in question (see Connections → Configure → Available Salesforce Objects) from the list → Add → Create → select Screens by the key of your JIRA project Id checking the corresponding check boxes → Update.
b. select 'Test Field (single line)' as a field type → name the field 'Object Identifier' → select Add → Create → select Screens by the key of your JIRA project by checking the corresponding check boxes → Update.
11. Under CONFIGURATION go to Bindings. Click +Add Binding.
Project: select JIRA Project to attach the connection.
Connection: select the connection created before
Click Add.
Skip the message 'Create Default Mappings to Salesforce Case' clicking Cancel.
Locate the created binding in the list → click Mapping. Click +Add Entity Mapping.
Issue Type: select the issue type that will be used for your JIRA-Salesforce Connector configuration
Salesforce Object: select the object
Click Add.
IMPORTANT: Create a mapping for each issue type/Salesforce object that will be in use for this configuration in your JIRA. Foe example, if you create 4 Salesforce objects and plan on tracking Service requests and Incidents, create 8 mappings based on JIRA Issue Type-Salesforce Object relation (see below).
Locate the mapping in question in the list → click Mappings to configure field mapping.
Connect mappings between Jira Field and Salesforce Object for every object to create associations:
AWS | Azure | GCP |
|---|---|---|
AWS Account: Object Identifier - Account ID | Azure Subscription: Object Identifier - Subscription ID | Google Project: Object Identifier - Project ID |
AWS EC2 instance: Object Identifier - Instance ID | Azure Virtual Machine: Object Identifier - VM ID | Google GCE Instance: Object Identifier - Google ID |
Click +Add to save the mapping pair → click Save.
Testing
Create a ticket, check the panel on the right → click Associate.
Select the object in ‘Object Identifier' and pick the existing CI in 'Salesforce Object' field.
ATTENTION: Object Type should be selected manually!