CMDB Mappings

Overview

CMDB Mappings connect GitHub repositories to Jira projects and teams. When a security finding is ingested, the CMDB determines which Jira project to create the issue in and which team owns the repository.

Why Mappings Matter

Without a mapping, findings for a repository are logged but cannot be escalated to Jira. The CMDB is the routing table that ensures the right team gets the right security ticket in the right project.

Viewing Mappings

The mappings table shows all configured mappings with the following columns:

  • Repository — the GitHub repository name or pattern.
  • Jira Project Key — the target Jira project.
  • Team Name — the team responsible for the repository.
  • Labels — shown as badges, these are applied to created Jira issues.
  • Default Assignee — the Jira user assigned to new issues by default.
  • Active — a green or yellow badge indicating whether the mapping is active.
  • Actions — Edit and Delete buttons.

A search bar at the top filters across repository name, project key, and team name.

Adding a Mapping

Click Add Mapping to open the creation form. Fill in the following fields:

  • GitHub Repository — an autocomplete dropdown with wildcard support. For example, org/api-* matches all repositories starting with api-in the org organization.
  • Jira Project Key — the Jira project key. Input is automatically uppercased.
  • Team Name — the name of the owning team.
  • Labels — a tag input field. Separate labels with a space or comma.
  • Default Assignee — a Jira user autocomplete field showing the display name and email address.

Editing a Mapping

Click Edit on any row to switch to inline editing mode. You can update the following fields:

  • Jira Project Key
  • Team Name
  • Labels
  • Default Assignee
  • Active status

Click Save to apply your changes or Cancel to discard them.

Wildcard Matching

Repository names support wildcard patterns. This lets you map multiple repositories to the same Jira project and team with a single mapping entry. For example:

org/frontend-*

This pattern maps all repositories starting with frontend- in the org organization to the same Jira project and team.