Jira Integration

Configure Jira integration to create and manage tickets for vulnerabilities from workflows or manually.

Configuration¶

Create a New Jira Integration¶

1. Go to the Integrations page from the left navigation menu.

2. Click the Jira integrations card in the Ticketing section.

3. Click + Create new integration.

4. Select your authentication method:

   • Jira Cloud: For cloud instances (for example, https://example.atlassian.net)
   • Jira Server: For self-hosted Jira instances

5. Fill in the form based on your authentication method:

   For Jira Cloud:

   • Name: A name to identify this integration
   • Jira instance's URL: Your Jira Cloud URL (for example, https://<organization-name>.atlassian.net)
   • Jira API token: Generate an API token from your Jira account

   API Token Type

   You can use either a standard API token or a scoped API token:

   • Standard token: Click "Create API token". No scopes need to be configured.
   • Scoped token: Click "Create API token with scopes". Select Jira as the app, then add the following scopes so the integration can create tickets, list projects, and manage issue data:

   Scope	Purpose
   read:jira-user	View user profiles (assignable users)
   read:jira-work	Read projects, issues, priorities, labels, statuses
   write:jira-work	Create and edit issues, add attachments, transition issues
   manage:jira-project	List and create project components

   • Jira account email: The email used to generate the API token

   

   For Jira Server:

   • Name: A name to identify this integration
   • Jira instance's URL: Your self-hosted Jira base URL (for example, https://jira.example.com)
   • Authentication: Choose Username & password or Personal access token

   Username & password

   • Username: Your Jira username
   • Password: Your Jira password

   Personal access token (PAT)

   Use this on Jira Data Center (and other self-hosted instances that expose PATs). Create a token in your Jira profile, then paste it into Personal access token. The account that owns the token needs the same project access as for username/password (at least one visible project, permission to create and update issues for workflow export).

   

6. Click Test Integration to verify the connection.

   The validation process tests your credentials by connecting to your Jira instance and fetching projects. Check the validation logs to see the results.

7. Click Connect Integration to create the integration.

To find your organization name for Jira Cloud, go to the Atlassian administration page > Click on Settings, then search for "Organization name".

Credential Validation¶

The Test Integration button tests your connection by fetching projects from your Jira instance.

When Validation Succeeds		When Validation Fails
When validation succeeds, you'll see: • Status: validation succeeded • A list of projects found in your Jira instance		When validation fails, check the validation logs for error messages. Common issues: • Invalid credentials: Verify your API token (Cloud), username/password (Server), or PAT (Server) • No projects found: Ensure your account has access to at least one project • Connection issues: Verify the instance URL is correct and accessible

Edit a Jira Integration¶

1. Go to the Integrations page from the left navigation menu.
2. Click the Jira integrations card in the Ticketing section.
3. Click the Edit (pen icon) button next to the integration you want to edit.
4. Update the fields you want to change.
5. Click Save to save.

Delete a Jira Integration¶

1. Go to the Integrations page from the left navigation menu.
2. Click the Jira integrations card in the Ticketing section.
3. Click the Delete (trash icon) button next to the integration you want to delete.

Using Jira in Workflows¶

Jira can be used as an export action in workflows to automatically create tickets when workflow conditions are met.

Configuration¶

When creating or editing a workflow:

1. Go to Workflows → Create (or edit an existing workflow)
2. In the Actions step, add an Export action
3. Select Jira as the integration type
4. Select your Jira integration from the dropdown
5. Configure the following:

Project and Issue Type¶

• Project: Select the Jira project where tickets will be created
• Issue Type: Select the issue type (for example, Bug, Task, Story)
• Parent Ticket (optional): Optionally select a parent ticket to create subtasks

Default Mappings¶

Unless Disable default mappings is enabled, Escape fills the following Jira fields:

• Summary: Set to the issue's full name

• Description: Automatically populated with:

  - Issue context (AI-generated context if available, otherwise the standard context)
  - Full remediation steps (AI-generated remediation if available, otherwise the default remediation)
  - Link to issue in Escape.tech
  

If you add a static mapping for the description field, your custom content will be prepended to the automatically generated description.

Disable default mappings removes the default summary and suppresses description generation entirely, including static and property description mappings. Supply a summary mapping if you enable it.

Property Mappings¶

Property mappings allow you to map Escape properties to Jira fields dynamically based on the issue data.

Available Escape properties for mapping:

Issue Properties:

• Severity
• Created At
• Name
• Category
• Context
• Status
• Full Remediation
• Targets
• Link in All Issues
• Link in Asset
• Link in Scan
• Link in Profile

Profile Properties:

• Profile Name
• Profile Scanner Kind

Asset Properties:

• Asset Name
• Asset URL
• Asset Tags
• Asset External URL
• Asset Type
• Asset Class

Custom Rule Properties:

• Custom Rule Name
• Custom Rule Link

For certain fields (Severity, Category, Status, Asset Class, Asset Tags, Asset Type), you can configure value mappings. This allows you to map specific Escape values to specific Jira field options. For example, you can map "Critical" severity to "Highest" priority in Jira.

Static Properties¶

Static properties mappings allow you to set fixed values for Jira fields regardless of the Escape issue properties. This is useful for fields that should always have the same value, such as assigning tickets to a specific team or setting a default component.

Required Fields¶

The system automatically detects required fields for the selected project and issue type. If any required fields aren't mapped (either through property mappings or static mappings), a warning will be displayed listing the unmapped required fields.

Usage¶

Creating Tickets From Workflows¶

New Issue and Manual workflows create tickets according to the configured mappings. Issue Updated workflows synchronize linked-ticket status.

Creation skips Ignored and False Positive issues. An export with only Ignored or False Positive issues fails. Existing tickets are skipped, including tickets from other workflows. Manual workflows can recreate a ticket only when it belongs to that workflow and Escape confirms it no longer exists in Jira.

Creating Tickets Manually¶

You can also create Jira tickets manually from the Ticketing sidepanel on any issue. This uses workflows configured with Jira export actions.

To create a ticket:

1. Navigate to an issue sidepanel
2. Open the Ticketing tab
3. Select a workflow that includes a Jira export action
4. Click Create Ticket

The workflow's Jira export action configuration (project, issue type, and mappings) will be used to create the ticket.

Filtering Issues By Ticket Presence¶

On the All Issues page, use Has Ticket to select issues with or without a linked ticket across supported providers, including Jira.

Bi-Directional Sync and Status Behavior¶

This section answers how Escape and Jira stay in sync when issues or tickets change state.

Jira → Escape (When a Ticket Is Closed in Jira)¶

When a Jira ticket linked to an Escape issue is closed in Jira (for example, moved to a "Done" status or given a resolution), Escape will resolve the corresponding issue the next time the Jira integration is pulled. Pull runs on a schedule (at least once per day per integration). If you reopen the ticket in Jira, the next pull will reopen the issue in Escape.

No workflow configuration is required for this direction: the sync is performed by the built-in Jira pull.

Escape → Jira (When an Issue Is Resolved or Updated in Escape)¶