| Info |
|---|
This article instructs you on explains how to configure Atlassian's Connector for Salesforce & Jira app in JIRA in order to associate CIs discovered by Cloudaware and your JIRA tickets. Built on force.com, 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.
| Table of Contents |
|---|
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. In your JIRA go . 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 → Add.
...
6. Log in to your Salesforce instance using your username and password*.
*If you don't have Salesforce password, log in to your 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.
...
Add more objects if necessary. Examples of objects and fields for different cloudscloud 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)
...
10. Create custom fields 'Object Type' and 'Object Identifier' in your JIRAJira.
To create a custom fields in JIRAJira, go to Settings (Gear icon) → Issues → select Custom fields 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 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 Jira project checking the corresponding check boxes → Update.
11. Under CONFIGURATION, go to Bindings. Click +Add Binding.
...
11.1. Select your JIRA Jira Project and the connection created before. Click Add.
...
11.2. Skip the message 'Create Default Mappings to Salesforce Case' by clicking Cancel. ??? (not offered)
11.3. Locate the created binding in the list → click Mapping. Click +Add Entity Mapping.
...
Select the issue type that will be used for your JIRAJira-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. Locate Select a mapping in question in the list → click Mappings to configure the fields mapping.
...
Samples of Jira Field-Salesforce Object mappings:
AWS | Azure | GCP |
|---|---|---|
AWS AccountID: Object Identifier - Account ID | Azure Subscription: Object Identifier - Subscription ID | Google Project: Object Identifier - Project Name |
AWS EC2 |
Instance: Object Identifier - Instance ID | Azure Virtual Machine: Object Identifier - VM ID | Google GCE Instance: Object Identifier - Google ID |
Testing
1. Create a test ticket.
...
5. The connector will populate the actual asset ID into 'Object Identifier' field in the JIRA Jira ticket.
...
6. 'Object Type' should be selected manually, so that it is populated in tickets.
...
| Tip |
|---|
Connector for Salesforce & Jira can enrich your JIRA Jira tickets with any CIs data. If you would like to To see more information available in the ticket, create custom fields and appropriate mappings (see step 11) in JIRA Jira to display details of the Salesforce object in question. For example, to add 'Instance Name' and 'Record ID' into JIRA Jira tickets related to AWS EC2 Instances, create so-named custom fields in JIRA 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). |
...