StackHawk Documentation StackHawk Logo HawkDocs

No results found

Try different keywords or check your spelling

Search documentation

Find guides, API references, and more

esc

Jira Cloud

jira

The Jira Cloud integration connects your StackHawk organization to Atlassian Jira, enabling you to create and track issues directly from scan findings. You can associate vulnerabilities with new or existing Jira issues without leaving the StackHawk platform.

Features

  • Issue creation: Create new Jira issues from scan findings with pre-populated vulnerability details
  • Issue linking: Associate findings with existing Jira issues for ongoing tracking
  • Multiple workspaces: Connect multiple Jira workspaces to a single StackHawk organization
  • Default configuration: Set default project and issue type per workspace

Requirements

StackHawk:

  • You must have a StackHawk account.
  • Your StackHawk Organization must belong to a plan with Jira Cloud support enabled. Reach out to StackHawk Support to enable it.

Jira:

  • You must have login permissions to the Jira workspace you wish to add the integration to.
  • You must have sufficient administration permissions to install add-ons to your Jira Cloud workspace.

Scopes

This integration requires the following Jira Cloud permissions:

  • Read access: View projects, issues, and issue types in your Jira workspace
  • Write access: Create and update issues, add comments
  • Delete access: Remove issue associations when findings are cleared

Setup

Install the StackHawk for Jira add-on from the Atlassian Marketplace, then connect it to your StackHawk organization.

  1. Log into StackHawk and go to the Jira Cloud Integration page.
  2. Click Enable Jira to generate a temporary integration token.
  3. Click View In Marketplace to open the Atlassian Marketplace in a new tab.
  4. Click Install and complete the installation process. Once finished, click Get Started to authorize the add-on.

Token Authorization

After installing the add-on, connect it to your StackHawk organization using a one-time token:

  1. Go to the Jira Integration page in StackHawk.
  2. Copy the integration token. This token expires after one hour.
  3. In Jira Cloud, navigate to Apps > Manage Your Apps > StackHawk for Jira > Get Started.
  4. Paste the token into the StackHawk Integration Token field.
  5. Your Jira workspace is now connected to your StackHawk organization.

StackHawk Jira integration connected

StackHawk integration token configuration

You can connect additional Jira workspaces to StackHawk. Each workspace can have its own default project and issue type for creating issues from findings.

StackHawk multiple connected workspaces

Verify Installation

To verify the integration is working:

  1. Go to the Jira Cloud Integration page.
  2. Look for Connected to: [your workspace URL], which confirms the integration is linked.

Usage

Send to Jira Cloud

To create or link a Jira issue from a scan finding:

  1. Navigate to Scans > Scan Details > Findings in StackHawk.
  2. Select the checkbox for a finding (Path, Status, Method).
  3. Click Actions > Send to Jira.
  4. Choose to create a new issue or link to an existing one.

Creating a Jira issue from StackHawk

Creating a new issue: Select the project and issue type. The issue will include vulnerability details from the finding. Click Create Issue to complete.

Linking to an existing Jira issue

Linking an existing issue: Search for and select an existing issue. A comment with the vulnerability details will be added to that issue. Click Link Issue to complete.

Jira issue created from StackHawk

Multiple workspaces: If you have multiple Jira workspaces connected, select the target workspace from the dropdown before creating or linking issues.

Selecting from multiple Jira workspaces

Other Actions

You can also change the triage status of findings (such as marking them as false positives or risk accepted) using the same selection workflow: select findings, then choose a different action from the Actions menu.

Populating Additional Fields in Jira

To automatically populate additional fields (such as Components or Assignee) on issues created from StackHawk, create a Jira Automation Rule. This requires Jira project administration permissions.

Basic rule (same values for all issues):

  1. In your Jira project, go to Project settings > Automation.
  2. Click Rules, then Create rule.
  3. For the trigger, select Issue created > Save.
  4. Add a condition: New condition > Issue fields condition.
  5. Configure the condition: Field: Creator, Condition: equals, Value: StackHawk for Jira.
  6. Add an action: New action > Edit issue and set the fields you want to populate.

Advanced rule (different values per StackHawk application):

  1. Complete steps 1-5 above.
  2. Add a branch: New branch > Branch rule / related issues > Current issue > Save.
  3. Add a condition: Issue fields condition with Field: Description, Condition: contains, Value: App: <your app name>.
  4. Add an action: Edit issue and set the fields for this application.
  5. Repeat steps 2-4 for additional applications.

See the Jira Automation documentation for more details.

Troubleshooting

Custom Fields on Jira Issue Types

If your Jira project uses custom fields on issue types, ensure those fields have default values configured. Without defaults, issue creation from StackHawk may fail.

Jira custom fields configuration

StackHawk supports custom fields for connected Jira workspaces. You can configure static custom field values for issues created from a specific workspace. Contact StackHawk Support for assistance with custom field configuration.

Removing the Integration

To disconnect the Jira Cloud integration:

  1. Go to the Jira Cloud Integration page in StackHawk.
  2. Click Remove Integration.
  3. In Jira, go to Apps > Manage Your Apps > StackHawk for Jira.
  4. Click Uninstall.

Feedback

Have suggestions, feature requests, or feedback? Contact StackHawk Support.

Your privacy settings

We use first and third party cookies to ensure that we give you the best experience on our website and in our products.