AppSpider Enterprise JIRA Integration

AppSpider integrates with JIRA cloud and on-prem so that security teams can automate work creation and assignment.

The automated ticketing feature simplifies this process while allowing you to:

  • Create targeted and precise tickets automatically with rules that can be reused across projects.
  • Customize ticketing templates to include as much security context as you need.
  • Let your remediation teams continue to use their existing tools and processes.

If you are looking for the JIRA integration for InsightAppSec, see Ticketing Integration.

One way JIRA integration

This integration is one way. If a ticket is updated in JIRA it does not change the status in AppSpider Enterprise.


  • JIRA username and password of a user with admin permissions.
  • A client in AppSpider you want to connect to.
  • URL of the JIRA instance you want to connect to.
  • The JIRA integration is set up on each client individually.

Set up an AppSpider JIRA integration

  1. Select your client from the Client dropdown in AppSpider and click OK.
  2. In the dropdown go to Administration > Integration.
  3. On the Integration page, click Add.
  4. On the Add Integration server page, fill in the information for your JIRA instance.
  • Server Type: This is always JIRA ADVANCED. JIRA ADVANCED works for on-prem and cloud.
  • Name: Name of your JIRA server
  • URL: URL where the JIRA server is located
  • Username: Your JIRA username
  • Password: Your JIRA password
  1. Click Connect to pull in the Issue Type, Issue Statuses, and Issue Priorities.

Issue Types, Issue Statuses, and Issue Priorities are mapped to a definition in your JIRA project. For example, if a vuln in AppSpider is marked as Verified, then you may want to put the ticket status in JIRA as In Progress. In the dropdown next to Verified, you would select In Progress.

To help you decide how to map them, here’s how we define Issue Types, Issue Statuses, and Issue Priorities in AppSpider.

  • Issue Type
    • Export as: The JIRA project issue type.
  • Issue Statuses
    • Verified: The issue was verified but not fixed.
    • Fixed: The issue was fixed. After the next scan, the status will change based on scan results.
    • Ignored: The issue was fixed, but the fix date is not available on the server. The issue will stay in the Ignored status until the date set, then the status changes based on the next scan results.
    • Unreviewed: The issue was not fixed. After the next scan, the status will change based on scan results.
  • Issue Priorities
    • Safe: This marks a redirection point in the application and not a vulnerability.
    • Informational: This is a best practice check. They are usually passive attacks.
    • Low: The issue has a low priority.
    • Medium: The issue has a medium priority.
    • High: The issue has a high priority.
  • Notes: This is an optional text box to add information about the JIRA server that is visible in AppSpider only.

Adding a JIRA server

  1. Click Save.


Congratulations, your JIRA integration is now set up and ready for use.

Send an issue to JIRA

After your integration is set up, you can send an issue to JIRA from the Discovered Issues table.

  1. Select the issues you want to send to JIRA.
  2. Click on the JIRA button at the top of the page.

Discovered issue

  1. In the popup box select the JIRA server and enter the project key.

Sending issues to JIRA

  1. Once the import is complete, the issues JIRA column will update with the current status.

Review JIRA issue status

Review your issue JIRA status from the Discovered Issues table.

Issue table

The JIRA column displays a check if the issue is imported into JIRA. You can filter the JIRA status by clicking the JIRA dropdown and selecting Imported or Not Imported.

Manage your JIRA integration

The Administration > Integration page contains all of your integrations, including JIRA.

Integration management

Use the Add, Edit, and Delete buttons to make changes to your integration.