Skip to main content

Connecting Hyperproof to Jira Cloud

Roles and permissions

  • Only administrators can configure Jira Cloud for their organization

Note: Hyperproof only supports certain Jira custom field types. See Supported Jira custom fields.

Note: If your Jira deployment changes from Jira Server or Jira Data Center to Jira Cloud, the integration will stop working, and all your integrated tasks will need to be set up again manually.

If you haven't reviewed the minimum required permissions yet, refer to Jira Cloud permissions.

Using an admin account versus a user account

Use admin account credentials when setting up the Jira integration. These credentials are saved in Hyperproof and used to set up the integration and to populate certain fields in the task window.
​

The Hyperproof user who's logged in and initially configures the admin user account for the integration is the sole owner of the credential settings. Other Hyperproof users cannot update the admin credentials. They can, however, click the Trash icon to delete and reset the saved admin credentials. It's highly recommended not to do this, as all existing task integrations will be deleted!
​

Any Hyperproof user who wants to use the task integration must go to the task window and set up a task to integrate with Jira. The first time they do this, they'll be prompted to log in to Jira. This is where they should use their own Jira login credentials, not the admin credentials.
​

User login credentials are saved in the back-end with the logged-in Hyperproof user. The recommended workflow is for each Hyperproof user who will integrate tasks with Jira to enter their credentials in the task window, as described above.
​

If a Hyperproof user needs to update their Jira credentials, they should go to Hyperproof Settings > Connected accounts. They should then locate the Jira task integration credentials card and disconnect. After they've disconnected, they can return to the task window, initiate a Jira interaction, and re-enter their credentials.

Connecting Hyperproof to Jira Cloud

Note: Only Hyperproof administrators can configure the Hypersync for Jira Cloud.

Your Jira administrator may need to be added to Hyperproof as a Hyperproof administrator to complete the initial app authorization during the connection configuration.

  1. From the left menu, select Settings.

  2. Select Integrations.

  3. Below Enabled, select Jira.

    The Jira window opens.

  4. Click Settings.

    jira-configure-settings.png

  5. Enter your organization's Jira URL, then click Submit.

    jira-cloud-submit.png

    Tip: Be sure to include the scheme, e.g., https://.

    The Authorize app window opens.

  6. Log in to your Jira account, then click Accept. If you see an error, verify the URL you entered in the previous step.

  7. Click Edit settings.

    The Jira settings window opens.

  8. Select the checkbox next to the Jira project or projects you want to connect, then click Next. Note that if you select more than one Jira project, you’ll need to map statuses for each project.

  9. From the drop-down menu, select a default issue type for each project, then click Next. Note that you can change the issue type when creating a new ticket.

  10. For each project, map a Jira status (e.g., To Do) to a Hyperproof status (e.g., Not Started) by dragging the Jira status to the Hyperproof status. Refer to the screenshot below for the recommended workflow.

  11. Click Next.

  12. Once all ticket-type statuses have been configured, the Optional mapping tab displays. Unless you are correcting a mapped user for a task created before August 2026, you do not need to make any changes. To make changes to mapped users, click View optional field mappings. Add or remove user or group mappings, clicking Next to move to the next tab.
    ​
    ​Note: Hyperproof can now assign tasks to Jira users who are not Hyperproof users. Therefore, mapping Hyperproof users to Jira users is no longer necessary.
    ​

  13. Click Save.

    Jira is now configured. Should you need to change any settings, such as default story type or mapping status, refer to Editing Jira settings.

Important tips to consider when mapping

Tips for the Jira to Hyperproof sync

  • If a Jira user changes the status of a Jira issue from In progress or To Do to one of the Completed statuses, the Hyperproof task status changes to Submitted.
    ​
    ​Note: Tasks can only be closed in Hyperproof. The Completed “bucket” of statuses ensures that Jira users are not able to close a task in Hyperproof. This action causes proof to land in the target object (e.g., a control).
    ​

  • If a Jira user changes an issue's status to one in the same bucket—e.g., from In progress to In testing, or from Not started to Needs triage—the Hyperproof status remains unchanged.

Tips for the Hyperproof to Jira sync

  • If a Hyperproof user changes the status of a task from Submitted to Closed or from Submitted to Canceled, the Jira status remains unchanged because both statuses fall into the Completed “bucket”. If the status is changed to Closed, the sync between Jira and Hyperproof will stop working until the task is reopened in Hyperproof.

  • If a Hyperproof user changes the status of a task from Submitted to In progress, or from Submitted to To Do, the Jira status changes to the first Jira status listed in the status map.

    Note: At this time, Hyperproof does not support complete Jira state transitions. For more information about status mapping, refer to Jira status mapping.

    Note: If you selected more than one Jira project, you’ll need to map statuses for each project.

Did this answer your question?