Skip to main content

​
Connecting Krait with Jira

This one-time setup for each workspace lets everyone in your Krait organization make issues directly in Jira Cloud.
You must be workspace OWNER / ADMINISTRATOR / MANAGER to connect or configure Jira to Krait.
1

Navigate to Integrations

Jira Integration Tab Pn
2

Provide Required Credentials

A integration panel will open on the right.
  • Provide the following required Jira connection details:
    • Domain: Your organization’s Jira instance URL.
    • User Name / Email: The authorized account for API access.
    • API Key / Token: A secure access key generated from your Jira account.
Provide Jira credentials to connect
  • Grant Krait permission to access your Jira workspace.
Once authorized Krait validates the settings promptly and confirms if the connection is successful.
jira_connect_success
3

Assign Integration to Resources

Admins can choose whether Jira Configuration should be:
  • Global (applies to all available resources)
  • Resource-specific (e.g., only for selected resources)
This ensures engineering teams receive tickets only for the resources they own.

​
Configuring Jira to Krait

There are two different options to configure Jira to Krait.

​
Jira Integration - Global Configuration

Global Jira configuration sets the default Jira Project and Issue Type for all new tickets created across the workspace. This ensures a consistent workflow even before team-specific settings are applied.

​
How to Configure Jira Globally

1

Connect Jira to Krait

Begin by authorizing Krait to access your Jira workspace. After successful authorization, you will see:
“Jira Connected Successfully - Your integration is now active. We’re synchronizing your data in the background.”
This indicates that your Jira metadata (projects, teams) is being pulled into Krait.
2

Select Default Project and Team

Choose the Jira Project where Krait should generate new issues by default. Then assign the team responsible for handling vulnerability tickets.
jira_global_configure_1
3

Save Configuration

Select Save Configuration to finalize.
jira_configure_success
All tickets generated across all resources in this workspace will follow this default mapping unless overridden at the resource level.

​
Jira Integration - Per-Resource Configuration

Per-resource Jira configuration allows you to override the global default by defining a project and team specifically for the selected resource (e.g., repository, container, cloud account, API endpoint). This is useful when different engineering teams maintain different components.

​
How to Configure Jira Per-Resource

1

Open Ticketing Configuration

Navigate to a vulnerability details page and select:
Configure your Ticketing System
linear_resource_configure_1
This opens a resource-specific configuration dialog.
2

Choose a project and team

Choose the Jira project where tickets for this specific resource should be created. Then select the Jira team responsible for handling those issues. Finally, click Submit to save the configuration.
linear_resource_configure_2
This configuration applies only to this specific resource. Krait will always prioritize per-resource settings over global defaults.

​
Disconnecting Jira

You can choose to disconnect Jira from Krait anytime you want.
Jira_disconnect
By disconnecting, you will lose access to the following Jira features within Krait:
  • Automatic issue syncing
  • All existing Jira connections
  • The ability to create new issues from Krait
You must be workspace owner or admin to disconnect Jira from Krait.