Skip to content

Connect Issue Tracker

SaaS Link Jira, GitHub Issues, GitLab, or YouTrack to auto-create remediation tickets.

Time: ~5 minutes

Why Connect a Tracker?

When SentriKat discovers a vulnerability, you want your team to act on it. Instead of manually creating tickets, SentriKat can automatically push remediation tasks to your existing issue tracker.

Each vulnerability → one ticket, with:

  • CVE ID and severity
  • Affected product and version
  • Remediation guidance
  • remediation due date (if applicable)
  • Link back to SentriKat for details

Supported Trackers

Tracker Auth Method Features
Jira Cloud API token Auto-create issues, sync status, custom fields
Jira Server/DC Personal access token Same as Cloud
GitHub Issues Personal access token Auto-create issues, labels by severity
GitLab Issues Personal access token Auto-create issues, labels, milestones
YouTrack Permanent token Auto-create issues, custom fields

Setup

1. Create an API Token

  1. Go to id.atlassian.com/manage-profile/security/api-tokens
  2. Click Create API token
  3. Give it a label like "SentriKat"
  4. Copy the token
  1. Go to Settings > Developer settings > Personal access tokens > Tokens (classic)
  2. Click Generate new token
  3. Select scopes: repo (for private repos) or public_repo (for public)
  4. Copy the token
  1. Go to User Settings > Access Tokens
  2. Create a token with api scope
  3. Copy the token
  1. Go to Profile > Account Security > Tokens
  2. Click New token with YouTrack scope
  3. Copy the token

2. Configure in SentriKat

  1. Navigate to Integrations > Issue Trackers
  2. Click + Add Tracker
  3. Select your tracker type
  4. Fill in:
    • URL: your instance URL (e.g., https://yourcompany.atlassian.net)
    • API Token: the token you just created
    • Project: which project to create issues in
    • Username/Email: your account (for Jira: the email associated with the API token)
  5. Click Test Connection to verify
  6. Click Save

3. Configure Auto-Creation Rules

After connecting, set up when tickets are created:

  1. Go to Integrations > Issue Trackers > your tracker > Rules
  2. Configure:
    • Minimum severity: only create tickets for Critical + High, or include Medium
    • Auto-assign: assign to a specific team member or leave unassigned
    • Labels/Tags: auto-tag with severity (e.g., critical, high)
    • Due date: use the published deadline as the ticket due date

Start Conservative

Start with Critical + High only. You can always lower the threshold later. Flooding your tracker with low-priority tickets leads to alert fatigue.

Verify It Works

  1. On the dashboard, find any active vulnerability
  2. Click Create issue (or wait for it to be created on the next scan)
  3. Check your issue tracker. The ticket should appear with all details

Next Step

Invite your team