Hackrate for Jira Cloud

Setup

1. Sign in to Hackrate as a program administrator.
2. Open the program’s Manage page and find Integrations → Jira Cloud.
3. Select Connect Jira Cloud and approve the requested Atlassian permissions.
4. Choose the Jira site, project, issue type, priority, and synchronization settings.
5. Save the configuration. Reports in that program can now create or link Jira issues.

Advanced configuration cheatsheet

All three advanced values must be valid JSON objects. Use double quotes, do not add comments or trailing commas, and use {} for an empty mapping.

Severity → Jira priority

Use the fixed Hackrate severity ID on the left and the Jira priority ID from your Jira site on the right. Jira priority names and IDs can be customized, so verify them in the Priority field of the Jira Cloud configuration.

Example using Jira's standard priority IDs:

{
  "1": "5",
  "2": "4",
  "3": "3",
  "4": "2",
  "5": "1"
}

• Left side: Hackrate severity ID.
• Right side: Jira priority ID.
• The default Jira priority is used when no severity mapping matches.
• Use numeric Hackrate severity IDs for bidirectional synchronization.
• The example assumes Jira IDs 5 = Lowest through 1 = Highest. Replace them if your Jira site uses different IDs.

Status → Jira workflow

Hackrate status IDs are fixed. Jira status names and transition IDs depend on the workflow of the selected project and issue type.

Example for a simple To Do → In Progress → Done Jira workflow:

{
  "2": {
    "jiraStatus": "To Do",
    "transitionId": "11"
  },
  "3": {
    "jiraStatus": "In Progress",
    "transitionId": "21"
  },
  "5": {
    "jiraStatus": "Done",
    "transitionId": "31"
  }
}

• The object key is the Hackrate status ID.
• jiraStatus is the Jira status name used when synchronizing Jira back to Hackrate.
• transitionId is the Jira workflow transition used when synchronizing Hackrate to Jira. It is not a status ID.
• Unmapped Jira statuses leave the Hackrate report status unchanged.

The short form {"5":"31"} is accepted for outbound-only status synchronization, but cannot map Jira status changes back to Hackrate.

Custom fields and assignees

{
  "fields": {
    "customfield_10042": "report.cvss",
    "customfield_10043": "report.cve",
    "customfield_10044": "report.target",
    "customfield_10045": "report.summary",
    "customfield_10046": "report.impact",
    "customfield_10047": "Created by Hackrate"
  },
  "assignees": {
    "hackrate-user-id": "jira-account-id"
  }
}

Custom-field mappings synchronize from Hackrate to Jira. The Jira field must already exist and accept a plain string. Structured Jira fields such as selects, users, options, and arrays are not supported by this mapping format.

Assignee mappings are bidirectional when Assignee synchronization is enabled. The left side is the Hackrate application user ID—not a nickname or email—and the right side is the Atlassian account ID—not a display name or email. Unknown mappings do not overwrite either assignee.

Checklist

• Keep severity, status, and custom-field mappings in their matching textareas.
• Enable the corresponding synchronization checkbox.
• Use IDs from the configured Jira Cloud site, project, issue type, and workflow.
• Use double quotes and remove comments and trailing commas.
• Test one linked report in both directions before rolling the mapping out broadly.

Data and permissions

Hackrate requests Jira permissions needed to read and update issues, comments, attachments, users, projects, and dynamic webhooks. OAuth access and refresh tokens are encrypted at rest. The integration only uses Jira sites explicitly approved during the Atlassian consent flow.

Disconnecting a program stops synchronization and does not delete existing Jira issues. See the Privacy Policy and Terms and Conditions for more information.

Support

For setup, security, or data-deletion questions, use the Hackrate contact page.