Jira Server permissions
Roles and permissions
Only administrators can configure Jira Server for their organization
Hyperproof supports both Jira Server and Jira Data Center. If your organization uses SSO for your Jira instance, please verify that it is able to accept incoming API and attachment requests (/rest/api and /secure/attachment, respectively).
To use Jira with Hyperproof, your Hyperproof administrator must first configure the integration.
Prerequisites
It’s recommended to perform the following actions prior to connecting Hyperproof to Jira Server.
Create two Jira service accounts (refer to Atlassian’s documentation here and here) to use specifically with Hyperproof. This ensures that in the primary instance, among other things, the integration can continue functioning if the configuring user leaves your organization. Creating a second service account is recommended in the event that Hyperproof developers need to debug a specific issue with your Jira service instance. This account should be created in your Jira testing environment rather than your production environment.
If your instance is on a private network, add Hyperproof’s static IP address (52.9.169.38) to your organization’s allowlist.
Turn off Jira login via CAPTCHA, if applicable.
Permissions
The permissions below need to be granted per user in each Jira project linked to Hyperproof.
Tip
Hyperproof’s Jira Server task integration supports personal access tokens that allow users to use Hyperproof's Jira integrations in instances where basic authentication has been turned off by Jira administrators.