Jira Accounts

Integrate Atlassian Jira with Cloudaware to discover issues, link them to CMDB configuration items, and support issue creation or updates from Cloudaware workflows.

info

• Audience: Cloudaware administrators, PMO/DevOps
• Outcome: The Jira account is connected and Jira issues are available in the CMDB for work tracking, operational context, and asset correlation

Capabilities

The integration supports:

• Discovery of Jira issues in the CMDB
• Relationships between Jira accounts, issue, and related assets
• Jira issue creation or updates from Cloudaware workflows, where configured

Prerequisites

Before you begin, make sure you have:

• Access to a Cloudaware account.
• A user with access to the Admin Console and permissions to manage cloud accounts, organizations, and integrations (Cloudaware Administrator).
• Jira Cloud or Jira Server URL.
• Jira API token or service credentials with read access.

note

If you use API tokens with scopes in Jira, ensure that the following Jira OAuth scopes are granted to Cloudaware:

• read:jql:jira
• read:jira-work
• read:issue:jira
• read:issue-meta:jira
• read:project:jira
• read:servicedesk-request
• read:request.feedback:jira-service-management
• read:user:jira
• write:jira-work
• write:request.feedback:jira-service-management
• write:servicedesk-request

Add a Jira Account to Cloudaware

To connect your Jira account to Cloudaware:

1. In Cloudaware, go to Admin.
2. Find Jira Accounts & Actions, then click + ADD.
3. Enter the following values:
   • Name: A display name for this connection.
   • URL: The Jira Cloud or Jira Server URL, e.g., https://jira.companyname.com.
   • Login: The Jira username.
   • Password: The Jira password (for cloud Jira, use API token).
   • Retrieve issues for the last: Select the desired time range from the drop-down list.
   • Trust Certificate: Enable if Jira is in a private network and TunHub has been set up by Cloudaware (in this case, the Jira URL has the format https://gw.tunhub.cloudaware.com:12345).
4. Click SAVE.
5. Confirm that the integration status indicator is green.

View Jira Data in CMDB

To browse discovered Jira resources:

1. In Cloudaware, open CMDB Navigator.
2. In the left pane, select JIRA.
3. Open an object list, e.g., Jira Issues, to view records.

Supported Objects

Cloudaware ingests the following Jira objects:

Jira Object	CMDB Object API Name
Jira Account	CA10__CaJiraAccount__c
Jira Issue	CA10__CaJiraIssue__c

Troubleshooting

note

Initial data collection may take time to complete.

Authentication Fails or Integration Shows Red Status

• Verify the Jira URL and API token or service credentials.
• Confirm that the Jira account has read access to the projects and issues Cloudaware must discover.
• Re-enter the credentials by editing the integration in Cloudaware.

Issues Are Missing

• Confirm that the Jira account can access the missing projects or issues in Jira.
• Review project permissions and issue security settings.
• In CMDB Navigator, verify that you are viewing the JIRA section and related resources.

Jira Workflow Actions Do Not Create or Update Issues

• Confirm that Jira actions are configured in Cloudaware.
• Verify that the Jira account has the required issue create or update permissions for the target project.
• Review the workflow criteria that trigger Jira actions.

Still stuck? Contact Cloudaware Support at support@cloudaware.com with the integration name and a brief description of the issue.

Reconfigure or Remove the Integration

warning

To rotate credentials, edit the existing integration instead of deleting and re-creating it.

Update the Integration Details

1. Go to Admin.
2. Select Jira Accounts & Actions.
3. Under the Jira Accounts tab, select the specific integration.
4. Open the three-dot menu (⋮), then click Edit.
5. Update the required fields.
6. Click Save.

Remove the Integration from Cloudaware

1. Go to Admin.
2. Select Jira Accounts & Actions.
3. Under the Jira Accounts tab, select the specific integration.
4. Open the three-dot menu (⋮), then click Delete.
5. Confirm the deletion if prompted.

Jira Actions

Jira actions use the connected Jira account to create or update Jira issues from Cloudaware workflows. Use them when CMDB records, policy findings, incidents, or other Cloudaware events need to open work items in Jira and keep those issues aligned with Cloudaware context.

Use case: A security team wants Jira issues to be created in a specific project when Cloudaware finds high- or critical-risk vulnerabilities on AWS EC2 instances. They also want comments added when the issues are fixed so Jira can close them automatically.

Jira Actions Prerequisites

Before you configure Jira Actions, make sure you have:

• A Jira account added to Cloudaware with green status.
• Jira permissions for the user or principal used by the Jira integration:
  • BROWSE_PROJECTS
  • CREATE_ISSUES
  • ADD_COMMENTS
• Salesforce Setup access in Cloudaware to configure outbound messages and flows.
• Field API names for the Cloudaware object that will trigger Jira issue creation, for example, CloudAware Vulnerability Scan fields.

tip

To find field API names, in Cloudaware, go to Setup → Object Manager, search for the object, open Fields & Relationships, and review the Field Name column.

Configure a Jira Action

Create a Jira Action to define the target Jira project, issue type, issue content, and optional comment content.

1. In Cloudaware, go to Admin.
2. Find Jira Accounts & Actions, then click CONFIGURED.
3. Open the Jira Actions tab.
4. Click + ADD JIRA ACTION.
5. Enter the following values:
   • Name: A meaningful name, for example, New Vulnerability Detected.
   • Jira Account: The Jira account configured in Cloudaware.
   • Project: The Jira project where issues will be created.
   • Issue Type: The Jira issue type, such as Bug, Task, or Incident, depending on your Jira configuration.
   • Summary: The Jira issue summary. You can use static text and sObject.<fieldApiName> references.
   • Description: The Jira issue body. You can combine static text with Cloudaware field values.
   • Comment: Optional comment text that Cloudaware posts to the related Jira issue when a later workflow sends another outbound message for the same record.
   • Field List: Optional list of field API names to exclude from the default Jira issue description. Prefix each excluded field with -, for example, -Id.
6. Click SAVE.
7. Copy and save the generated endpoint URL. You will use it when configuring the outbound message.

note

Do not exclude fields that Cloudaware needs for mapping between Cloudaware records and Jira issues. This mapping is required to associate Cloudaware CMDB records with Jira issues.

Jira Action Expression Examples

Jira Action fields can reference the triggering Cloudaware record as sObject.

Input	Result
This is a text	Sends static text.
sObject.Name	Sends the value of the triggering record's Name field.
'New Vulnerability Detected: ' + sObject.CA10__name__c + ' ' + sObject.CA10__cve__c	Combines static text, vulnerability name, and CVE value in the issue summary.
'*AWS EC2 Instance ID*: \n*' + sObject.CA10__instanceId__c + '*'	Uses Jira formatting and newline characters in the issue description.
-Id	Excludes the Id field from the default field list appended to the Jira description.

Cloudaware appends outbound message fields to the Jira description in this format:

Field Label 1: Field Value 1
Field Label 2: Field Value 2

Use Field List to exclude fields that are already included in your custom description or should not be sent to Jira.

Create an Outbound Message

After saving the Jira Action, create an outbound message that sends selected Cloudaware record fields to the Jira Action endpoint.

1. In Cloudaware, go to Setup (under the gear icon).
2. In the Quick Find bar, search for Process Automation.
3. Under Workflow Actions, select Outbound Messages → click New Outbound Message.
4. From the drop-down list, select the object (in this example, CloudAware Vulnerability Scan). Click Next.
5. Configure the outbound message:
   • Name: A descriptive name, for example, Jira Issue: New Vulnerability.
   • Endpoint URL: Paste the endpoint URL generated by the Jira Action.
   • Selected Fields: Move every field referenced in the Jira Action Summary, Description, or Comment from Available Fields to Selected Fields. The record Id is included by default.
6. Click Save.

warning

If a field referenced in the Jira Action is not included in Selected Fields, Cloudaware may send undefined to Jira for that value. The order of selected fields is preserved in Jira.

Set Up a Flow to Create Jira Issues

Set up a record-triggered flow that calls the outbound message when a Cloudaware record meets your criteria.

The example below creates Jira issues for high-risk vulnerability records.

1. Proceed in the Salesforce UI (Cloudaware Setup).
2. In the Quick Find bar, search for Flows.
3. Under Process Automation, select Flows, then click New Flow.
4. Select Record-Triggered Flow, then click Create.
5. Select the source object, for example, CloudAware Vulnerability Scan.
6. Configure the trigger:
   • Trigger: A record is created.
   • Condition Requirements: All Conditions Are Met (AND).
   • Example condition: Severity greater than or equal to 7.
7. In Optimize the Flow for, select Actions and Related Records.
8. Add an Action.
9. Select Outbound Messages, then choose the outbound message created earlier.
10. Name the action, for example, Create Issue For New Vulnerability Detected.
11. Save and activate the flow.

Create a Flow to Post Jira Comments

Cloudaware can post a comment to an existing Jira issue when the triggering record changes, for example, when a vulnerability is fixed.

Before you begin, confirm:

• The Jira Action Comment field is configured.
• Tthe outbound message includes every field referenced in the comment, for example, CA10__disappearanceTime__c.

1. In Cloudaware Setup, create another Record-Triggered Flow.
2. Select the same source object used for issue creation.
3. Configure the trigger:
   • Trigger: A record is updated.
   • Condition Requirements: All Conditions Are Met (AND).
   • Example condition: IsDeleted equals True, or another field that represents the resolved state in your workflow.
   • When to Run the Flow for Updated Records: Only when a record is updated to meet the condition requirements.
4. In Optimize the Flow for, select Actions and Related Records.
5. Add an Action.
6. Select Outbound Messages, then choose the outbound message used by the Jira Action.
7. Name the action, for example, Post Comment When Vulnerability Is Fixed.
8. Save and activate the flow.

After comments are posted, Jira automation can use those comments or field values to transition, close, or bulk-update related Jira issues.

Security Notes

• Use a dedicated Jira service account or API token for Cloudaware discovery and workflow actions.
• Grant only the minimum project and issue permissions required for the Jira data and actions Cloudaware must use.
• Avoid using a personal administrator account for long-running integrations.
• Rotate tokens or service credentials according to your organization's credential-rotation policy.
• Update the Cloudaware Jira integration immediately if credentials are revoked, regenerated, or reset in Jira.

Related

• CMDB
• Webhooks & Events