| Info |
|---|
This guide explains how to add a Jira account to Cloudaware and configure actions for Cloudaware to automatically discover Jira issues in the CMDB and/or create issues in Jira based on specified criteria. |
To see how Cloudaware seamlessly integrates with Jira in action, request a demo.
...
Cloudaware offers several key capabilities of integrating with Atlassian Jira:
Auto-discovery of Jira issues related to specific CMDB objects and importing them from Jira to Cloudaware
Creating a Jira issue whenever any specific criteria are met in Cloudaware (e.g. new incident, policy violation, vulnerability scan, etc.) and posting a comment to the existing Jira issue, e.g. new vulnerability has been detected as fixed, etc.)
Configure auto-discovery and import of Jira issues to Cloudaware CMDB
...
| Tip |
|---|
Object identifier is a cloud provider ARN for that object, for example: Object Type: AWS ELB Load Balancer |
In order to view a list of CMDB objects, navigate to Setup → type Objects in the Quick search bar.
...
| Note |
|---|
*The custom Jira field |
...
should be a text/string. |
Add these two fields to Jira issues using instructions provided by Atlassian here. It's possible to set Set the values for these custom fields manually or using internal Jira processes.
Configure auto-creation of Jira issues from Cloudaware
...
Manage permissions and create fields in Jira
1. Grant Cloudaware with user/project: ADD_COMMENTS permission (see Jira documentation).
2. Log in to Cloudaware account → Setup → Objects.
3. Select an object you want Jira issues to be created for (in this example, CloudAware Vulnerability Scan).
4. Review the section 'Custom Fields & Relationships' to define fields that should be displayed in an issue's description. In our use case we are using the following fields: Priority, Risk, Severity, CVSS Number, Host, Port, Protocol, Description, Disappearance Time.
| Note |
|---|
Use Cloudaware Field Label names when creating fields in your Jira as fields names MUST match. |
Set up Jira Actions in Cloudaware
| Anchor | ||||
|---|---|---|---|---|
|
...
Field List - determine the fields you'd like to be displayed in a Jira issue and Cloudaware comment.
| Note |
|---|
Use API names for fields. The integration must include all the fields you plan to use in notifications. The order you choose for the fields will be reflected in a Jira issue. |
Click Save.
5. Copy and save the URL as it is required for further configuration in Cloudaware.
...
Configuring Cloudaware workflows to create issues and post comments in Jira
| Anchor | ||||
|---|---|---|---|---|
|
Once you have configured Jira Action, set up two different workflow rules － for creating a Jira issue (1) and adding a comment (2).
1. Workflow Rule for Jira issue creation:
...
Click Save&Next.
Add Workflow Action → New Outbound Message:
Object: CloudAware Vulnerability Scan
Name: Jira Notification: New Vulnerability Detected
Endpoint URL: paste the URL copied from the integration's details
Select the fields to be displayed as set up in the Integration details:
...
Note that Name is a mandatory field.
Click Done. Click Activate to activate your workflow.
2. Workflow Rule for posting a comment in Jira issue:
...
Object: CloudAware Vulnerability Scan
Name: Jira Notification: Vulnerability Fixed
Endpoint URL: paste the URL copied from the integration's details
Select the fields to be displayed as set up in the Integration details:
...
Click Done. Click Activate to activate your workflow.
Jira issue sample | Cloudaware comment sample |
|---|---|
 |  |
...
Bulk close Jira issues with Cloudaware comments
Based on our use case, we can consider all issues with a comment as not requiring further actions since a vulnerability the Jira issue informs of has been fixed.
Follow these steps to configure automatic change of issue status to 'Resolved':
In your Service Desk project select Project settings → Automation.
Select Add rule.
Select Custom rule from the list, then select Next.
Give your custom rule a name and a description.
Configure your rule by defining the WHEN, IF, and THEN fields:
5.1. When comment added
5.2. If comment contains This vulnerability is fixed and deleted on
5.3. Then transition issue to status "Resolved"
...
Populate custom fields in Jira
| Anchor | ||||
|---|---|---|---|---|
|
This option requires having custom fields Object Type, Object Identifier and fields that were created for Jira actions.
Based on our use case, we can consider having all custom field values populated automatically. This will also provide a great visibility in Cloudaware CMDB as each Jira issue will be linked to a CMDB record.
...