Setting Multiple Jira Integrations

If you have multiple HackerOne programs, you can integrate them to the same Jira instance whether you’re using the Jira Server or Jira Cloud integration.

To integrate multiple HackerOne programs to the same Jira instance:

  1. Remove the “HackerOne for Jira” plugin only if you’re currently using Jira Cloud.
    a) Go to Jira.
    b) Navigate to Jira settings > Apps > Manage Apps.
    c) Click on the HackerOne for Jira app.
    d) Click Uninstall.

uninstall Jira plugin

  1. Navigate back to HackerOne.
  2. Go to Program Settings > Program > Integration.
  3. Click the Connect with Jira link.
  4. Choose Jira Server and you’ll be redirected to this 4-step setup screen where you can configure your Jira integration.



  1. Navigate to the Configure Application Links console of Jira by going to Jira Settings > Products > Application links.

Configure Application Links

  1. Enter to the field.
  2. Click Create new link.
  3. Ignore the warning message.

Configure Application URL window

  1. Click Continue.
  2. Enter HackerOne for the Application Name.

Link Applications window

  1. Enter Generic Application for the Application Type.
  2. Click Continue.
  3. Click on the pencil icon on the Configure Application Links page to edit the HackerOne application.

Edit HackerOne on the Configure Application Links page

  1. Select Incoming Authentication on the left sidebar.

Incoming Authentication setup

  1. Enter the following information on the Incoming Authentication section of the Configure HackerOne window:
Field Details
Consumer Key HackerOne JIRA Client
Consumer Name HackerOne
Public Key Copy and paste from the key below

HackerOne Jira public key

-----END PUBLIC KEY-----
  1. Click Save.
  2. Navigate back to HackerOne and enter the URL of the Jira instance you want to authenticate with in the Instance base URL field in the Configure an Application Link step. jira-server-14
  3. Click the Authenticate with Jira button to finalize the setup between HackerOne and your Jira instance.
  4. Configure which HackerOne projects you'd like to escalate to Jira in the Configure HackerOne to Jira escalation window.

    • Select the Allow me to select a project every time when I escalate an issue checkbox to have the ability to select from multiple projects when creating Jira issues.
    • Select the Jira Priority you want to map to the corresponding HackerOne severity. This enables the right priority to be set when escalating a HackerOne report to Jira.


  1. (Optional) Select which Jira actions you'd like to post onto HackerOne in the Select Jira to HackerOne events window. You can choose from:
Option Detail
Status changed Post an internal comment when an issue changes status.
Resolution changed Post an internal comment when an issues changes resolution.
Priority changed Post an internal comment when an issue changes priority.
Assignee changed Post an internal comment when an issue changes assignee.
Comment added Post an internal comment when someone comments on an issue.
Closed issue status Resolve the report when an issue is closed with the selected status.


  1. (Optional) Select which actions in HackerOne you'd like to post to Jira in the Select HackerOne to Jira events window. You can choose from:
Option Detail
Comments When someone comments on a report, post an update on the associated Jira issue.
State Changes When someone changes the state of a report, post an update on the associated Jira issue.
Rewards When someone awards or suggests a bounty and/or bonus, post an update on the associated Jira issue.
Assignee Changes When someone assigns a user/group to a report, post an update on the associated Jira issue.
Disclosure When disclosure is requested or a report becomes public, post an update on the associated Jira issue.
Synchronize attachments Synchronize attachments linked with reports and comments to the associated Jira issue.


  1. Follow steps 20-24 for each subsequent program you need to add an integration for. Note:You only need to follow steps 20-24 for your other programs because the application link has already been created when integrating with your first program, and only 1 application link is needed to set up a Jira integration.