Jira Integration and usage guide

Overview

This guide explains how to integrate Jira with the Matters Dashboard to track alerts, misconfigurations, and sensitive data.

By integrating Jira, security analysts can efficiently manage risks and track actionable items across relevant teams.

Steps to Integrate Jira on Matters Dashboard

Step 1: Navigate to Jira Integration

1. Log in to the Matters Dashboard

2. Click on Project Settings (bottom-left corner)

3. Navigate to Notifications > Jira

Step 2: Choose Integration Type

Integration can be done in two ways:

Procedure A: New Integration Flow

1. Click on Add Project → Select New Integration

2. Enter the following details:

• Jira Domain (e.g., https://your-domain.atlassian.net)

• Admin Email

• Jira Access Token (Create from: https://id.atlassian.com/manage-profile/security/api-tokens)

• Optional: Token Expiration Date

3. Click Continue Setup

Procedure B: Existing Integration Flow

1. Click on Add Project → Select Existing Integration

2. Project details will be auto-populated

3. Verify the details

4. Click Continue Setup

Step 3: Configure Jira Project

1. Select:

   • Jira Project (Space)

   • Work Type

2. Enable ticket creation for:

• Misconfigurations

• DAM Alerts

• DDR Alerts

3. Add filters for each type if required

4. Click Continue Setup

Step 4: Mapping and Configuration

4.1 Field Mapping

a. Severity Mapping → Priority

• Map the severity levels in Matters to the corresponding priority levels in Jira.

• This ensures that the importance of an alert or issue is correctly represented in Jira.

Example:

• Matters Critical → Jira Highest

• Matters High → Jira High

• Matters Medium → Jira Medium

• Matters Low → Jira Low / Lowest

This mapping helps Jira users quickly understand the urgency of issues based on priority.

b. Status Mapping

In this step, you need to configure status mapping between Matters and Jira.

• You will map the status from Matters (such as Open or Resolved) to the corresponding status in Jira.

• This ensures that when a ticket is created or updated, the correct status is reflected in Jira.

For example:

• Matters Open → Jira In Review/Todo/In Progress

• Matters Resolved → Jira Done

This mapping helps maintain consistency between both systems and ensures that ticket status is correctly synced.

4.2 Ticket Creation Mode

In this step, you decide how Jira tickets should be created.

• Auto (Automatic): Jira tickets will be created automatically whenever a new alert, misconfiguration, or issue is detected based on your configuration and filters.

• Manual: Jira tickets will only be created when the user clicks the “Push to Jira” button from the UI.

Note: If Auto mode is selected, manual ticket creation will not be available.

4.3 Ticket Closing Permissions

This setting controls how ticket closure is synchronized between Matters and Jira. It helps ensure that ticket status remains consistent across both platforms.

You will see two options here:

1. Matters → Jira

Enable this option if you want Jira tickets to be automatically closed when the corresponding alert, misconfiguration, or issue is marked as closed in the Matters Dashboard.

2. Jira → Matters

Enable this option if you want the status in Matters to be updated when the linked Jira ticket is closed in Jira.

Note: You can enable either one-way sync or both directions, depending on how your team manages tickets and workflows.

Once Configured click on Save

4. Ticket Status Sync Mapping

This section allows you to define how statuses in Matters should correspond to statuses in Jira.

Since Matters and Jira may use different status names, this mapping ensures that when a status is synced, it is translated correctly between both systems.

For example:

• Open in Matters can be mapped to To Do in Jira

• Resolved in Matters can be mapped to Done in Jira

4.5 Save Configuration

Push to Jira feature

The Push to Jira feature allows users to manually create Jira tickets directly from the Matters Dashboard for specific alerts or misconfigurations.

This feature is available only when Manual Ticket Creation is enabled during Jira configuration.

A. Create Jira Ticket for Misconfigurations

Follow the steps below to create a Jira ticket for a misconfiguration:

1. Navigate to Misconfigurations from the dashboard.

2. Select the specific misconfiguration for which you want to create a Jira ticket.

3. Go to the Affected Data Stores section.

4. Click on “Push to Jira” for the specific data store where you want to raise the ticket.

5. Once clicked:

• A Jira ticket will be created successfully.

• The ticket will be visible in the Matters UI.

6. You can:

• Click on the Jira ticket link from the UI

• This will redirect you to the Jira platform

• Validate the ticket details such as fields, description, and status

B. Create Jira Ticket for DDR Alerts

Follow the steps below to create a Jira ticket for DDR alerts:

1. Navigate to DDR Alerts.

2. Select the specific alert for which you want to create a Jira ticket.

3. Click on “Push to Jira” (available within the alert details page).

Once clicked:

• A Jira ticket will be created for the selected alert

• The ticket will be reflected in the UI

C. Create Jira Ticket for DAM Alerts

Follow the steps below to create a Jira ticket for DAM alerts:

1. Navigate to DAM Alerts.

2. Click on “Push to Jira”.

3. Once clicked:

• A Jira ticket will be created successfully

• The ticket will be visible in the UI

4. You can open the ticket in Jira to validate the information and track the issue.

That’s it — your Jira integration is now set up and ready to use.

You can start creating and tracking tickets directly from the Matters Dashboard.