Jira integration requirements

  • Public preview

Before installing XBOW Integration for Jira, confirm that you have the required Jira and XBOW access.

Jira requirements

You need:

  • A Jira Cloud site where you have site admin access
  • A Jira project and issue type where XBOW work items should be created
  • Permission for the app to create work items, add comments, read Jira metadata, and write issue properties

You can use an existing Jira project if your team already tracks remediation there. Use a dedicated project if you want clearer ownership, reporting, permissions, or workflow rules for XBOW-created work items.

The integration does not support Jira Server or Jira Data Center.

XBOW requirements

You need:

  • An XBOW organization.
  • The XBOW region for that organization: US, EU, or SG. To identify your region, check the URL you use to sign in to Console. See Identify your region.
  • The XBOW organization ID. Copy it from your Console URL: https://console.xbow.com/v2/organizations/ORGANIZATION-ID (your base URL varies by region).
  • An XBOW API token for that organization. To generate one, see Generate an API key in the API reference.

Use a dedicated XBOW API token for this Jira integration. Do not reuse a token from another integration or another Jira site.

If you do not have an XBOW organization, contact your XBOW customer success manager.

Mapping requirements

The Jira administrator chooses the project and issue type. The app then checks Jira metadata to confirm the mapping can create work items.

When Jira requires extra fields, the app can show and configure supported field types, including:

  • Text
  • Textarea
  • Number
  • Date
  • Single select
  • Multi select
  • Components
  • Versions
  • Fix versions

To maintain data integrity, the integration cannot map data to other types of Jira field. All other fields are unsupported, for example: assignee, reporter, user fields, group fields, sprint, team, parent or sub-task fields, Jira Service Management request fields, Assets or Insight fields, security levels, and unknown custom field shapes.

If the project or issue type you want to use for XBOW findings requires data for a field that the XBOW app does not support:

  • Configure a default value in Jira, for example: reporter: XBOW or assignee: security-triage-team
  • Make the field optional
  • Choose a different project or issue type

Next steps

Was this helpful?