Threatrix Documentation
Threatrix
  • Getting Started
  • Developer Quick Start
  • SecureShip
    • Artifactory Scanning
    • ThreatAgent Scanning
  • Threat Center
    • Creating Account
      • OAuth Login
    • Entity Dashboard
    • User Profile
  • AICertify
    • Reviewing Results
  • codecertify
    • Quick Start
    • Project Summary Tab
    • Components Tab
      • Custom Components
        • Adding
        • Editing
        • Important Notes
      • Header Panel
      • Module Tree Panel
      • Results Panel
        • Card View
        • Risk Graph View
      • Audit History
    • Assets Tab
      • Custom Asset Matches
        • Adding Asset Match
  • securecore
    • Project Dashboard
    • ThreatScan
    • Scan Results
  • Threat Agent
    • Threat Agent Overview
    • Threat Agent - Installation & Scanning
    • Scan Summary Reports
    • Resolving Errors
    • Scanning Container Images
  • Integrations
    • Dependency Managers
      • RENV
    • Build Integrations
      • AWS CodeBuild
      • Azure DevOps
      • Bitbucket Pipeline
      • CircleCI
      • GitHub Action
      • GitLab Pipeline
      • Jenkins Pipeline
    • SCM Integrations
      • GitLab
      • Bitbucket
    • Issue Management
      • Jira
    • Notifications
  • Policy Management
    • Policy Overview
    • Creating Policies
    • Policy Conditions
    • Policy Actions
    • Policy Scopes
  • Administration
    • User Management
    • Organization Settings
      • Organization Knowledge Base
      • Integration
        • Slack Integration
        • Jira Integration
        • Service Keys
    • RBAC
    • Entity Management
    • Okta
      • Okta Org2Org Integration
  • GraphQL API
    • API Overview
  • Resources
    • Dependency Managers
      • PIP
    • Dictionary
    • Licenses
    • Security & Privacy
    • Binary File Support
  • Hybrid / On Premise
    • Getting Started
    • Installation
    • Upgrade
    • Setup
    • Cloud Data Disclosure
    • Troubleshooting
Powered by GitBook
On this page
  • Getting Started
  • Project URL
  • Project Key
  • Issue Type
  • Create Jira Token
  • Setup Integration
  • Creating Jira Tickets

Was this helpful?

  1. Integrations
  2. Issue Management

Jira

PreviousIssue ManagementNextNotifications

Last updated 1 month ago

Was this helpful?

Getting Started

You'll need the following data to being your integration with Jira

  • Project URL

  • Project Key

  • Issue Type

  • login/email for account

  • Jira API Token

Project URL

You can get your project URL from the browswer by navigating to your project and copying the portion of the URL that reflects the only the domain name for your Jira account, as shown below:

Project Key

Your project key can be retrieved from your project settings at under your details tab:

Issue Type

Issue types are found in Jira under you project settings Issue Types menu. Default Jira issues types are: Epic, Task and Subtask

Create Jira Token

The first step is to create a Jira token that can be used with your Threatrix integraition. We suggest creating a service accont that can be used for this purpose, but any user account, with appropriate privledges, can be used for this purpose.

  1. Click "Create New Token" button and give it a name and expiration date. Be aware that your Threatrix integration will stop functioning after the token expires.

  2. Be sure to Copy the token and store it somewhere safe. \

Setup Integration

Now that we have all of the necessary data to contiguration the integration, let's get started.

  1. Login to Threatrix Threat Center and navigate to Admin -> Settings -> Integration -> Jira Integration

  2. Enter the values collected in the previous steps

  3. Click "Save" to commit the changes.

And, now you're ready to create tickets from Threat Center!

Creating Jira Tickets

Jira tickets can be created in three ways:

  1. Directly from the Vulnerability details screen. Once the ticket is created, a link to the Ticket will be added to the license details screen.

  2. Directly from license details screen:

    Once the ticket is created, a link to the Ticket will be added to the license details screen.

  3. Automatically from within polices. From withing policies, edit the policy for which you'd like to create a Jira ticket. Edit the policy and Navigate to the actions tab. Select "Add new action" and then select "Issue" from the Action drop down and Type Jira. You may also add notes to the policy which will flow through to the Jira ticket to provide guidance to your development team.

Login to Jira and Navigate to `Atlassian Account -> Security -> Create API Tokens` or just use this link.

https://id.atlassian.com/manage/api-tokens
Project Key
Succesful Jira Integration
Create Jira ticlet from License Details