...
| Info |
|---|
This article explains how to configure Atlassian's Connector for Salesforce & Jira app to associate CIs discovered by Cloudaware and Jira tickets. This app is for cloud, server and data center Jira. |
To see how Cloudaware seamlessly integrates with Jira in action, request a demo.
| Table of Contents |
|---|
Introduction
Cloudaware CMDB is built on Force.com. Cloudaware manages the discovered cloud and on-prem inventory items as Salesforce custom objects and fields. These objects and fields can be used to enrich Jira tickets with any information from Cloudaware CIs.
Prerequisites
Add Jira account to Cloudaware.
Go to the Jira marketplace to locate the app Connector For Salesforce & Jira. Make sure to have familiarized with the pricing
...
and free trial terms before adding the app to your
...
Jira instance.
...
Install the app to your Jira instance.
Configure the app
1. Log in to Jira. Go to Apps → Salesforce.
...
2. Under CONFIGURATION, go to Connections. Click +Add Connection.
...
3. Give a meaningful name to 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 using username and password*.NOTE:
*If you don't have
...
Salesforce password, log in to
...
Cloudaware account
...
. Select Setup → Users → locate your user (check the username) → 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' by 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 in question from the list → . Click Next.
...
Select the fields available on the object in question → +Add. Thу selected fields will be used in JIRA tickets for further association of tickets and CIs.NOTE: 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.
Click Next. Once all fields are added, click Next.
Add more objects if necessary. Examples of objects and fields for different cloud providers:
Cloud | AWS | Azure | Google Cloud | |||
|---|---|---|---|---|---|---|
Object | AWS Account | AWS EC2 Instance | Azure Subscription | Azure Virtual Machine | Google Project | Google GCE Instance |
Fields | Account Name Account ID Role Status: Collector Deleted | Instance Name or ID Instance ID State Name Deleted from AWS | Subscription Name Subscription ID Status (Collector) | Azure Virtual Machine Name VM ID Power State Deleted from Azure | Google Project Name Status (Collector) | 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 ?]
...
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 → under FIELDS on the left, select 'Custom fields' → Create custom field:
a. Choose 'Select List (single choice)' as a field type → Next → name the field 'Object Type' → in 'Options' select every field in question (check Connections → Configure → Available Salesforce Objects) from the list → Add → Create → select Screens by the key of your Jira project checking the corresponding check boxes → Update.
b. select 'Text Field (single line)' as a field type → name the field 'Object Identifier' → select Add → Create → select Screens by the key of your Jira project checking the corresponding check boxes → Update.
11. Under CONFIGURATION, go to Bindings. Click +Add Binding.
Project: select JIRA Project to attach the connection.
...
11.1. Select your Jira Project and the connection created before. Click Add.
...
11.2. Skip the message 'Create Default Mappings to Salesforce Case' by clicking Cancel.
11.3. Locate the created binding in the list → click Mappings.Issue Type: select Mapping. Click +Add Entity Mapping.
...
Select the issue type relevant to your settings
Salesforce Object:
IMPORTANT: that will be used for your Jira-Salesforce Connector configuration and the Salesforce object. Click Add.
...
| Note |
|---|
Create a mapping for each issue type |
...
-Salesforce object that will be in use for this configuration in |
...
Jira. For 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 the example below: |
...
11.4. Select a mapping in the list → click Mapping Mappings to configure field the fields mapping.
Connect Set up mappings between Jira Field and Salesforce Object for every object to create associations.
...
Click +Add to save the mapping pair → click Save.
Samples of Jira Field-Salesforce Object mappings:
!!! Object Identifier - Instance ID !!! (required)
Click Save.
ATTENTION: Object Type should be selected manually. Create a custom field.
To create a Custom Field in JIRA:
Go to Settings (Gear icon) → Issues → Custom fields under FIELDS (on the left) → Create custom field → Select List (single choice) → Next → set the name as 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 за your JIRA project по checking the corresponding check boxes → Update.
Open a ticket,
AWS | Azure | GCP |
|---|---|---|
AWS AccountID - Account ID | Azure Subscription - Subscription ID | Google Project - Project Name |
AWS EC2 Instance - Instance ID | Azure Virtual Machine - VM ID | Google GCE Instance - Google ID |
Testing
1. Create a test ticket.
2. Open the ticket and check the panel on the right → click Associations.
...
3. Click Associate.
...
4. Select the object in 'Object typeIdentifier' field and the existing pick a CI in ‘Salesforce Object’ → Associate.'Salesforce Object' field.Click Associate.
...
5. The connector will populate the actual asset ID into 'Object Identifier' field in the Jira ticket.
...
6. 'Object Type' should be selected manually, so that it is populated in tickets.
...
| Tip |
|---|
Connector for Salesforce & Jira can enrich Jira tickets with any CIs data. To see more information in the ticket, create custom fields and appropriate mappings (see step 11) in Jira to display details of the Salesforce object in question. For example, to add 'Instance Name' and 'Record ID' into Jira tickets related to AWS EC2 Instances, create so-named custom fields in Jira and map them in the following pairs: 'Instance Name' (Jira Field) - 'Instance Name or ID' (Salesforce Field) and 'Record ID' (Jira Field) - 'Record ID' (Salesforce Field). |
