![Hyperproof.Io [Test] Help Center](https://downloads.intercomcdn.com/i/o/xgk1dxp2/757668/427b255f2659cc7e0853d6a00ec1/628914ae2617199b7d999ba797a5305a.png)
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, verify that it can accept incoming API and attachment requests (/rest/api and /secure/attachment, respectively).
To use Jira with Hyperproof for task integration, your Hyperproof administrator must first configure the integration.
Prerequisites
Perform the following actions before 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 if Hyperproof developers need to debug a specific issue with your Jira service instance. This account should be created in your Jira testing environment instead of your production environment.
Turn off Jira login via CAPTCHA, if applicable.
If your instance is on a private network, add the static IP address for the Hyperproof instance where your organization is hosted to your company's allowlist.
Hyperproof US IP addresses - 20.184.128.53, 52.9.169.38, 52.159.252.1
Note: IP address 52.9.169.38 will be deprecated and replaced with 52.159.252.1 in the future. To prevent connectivity issues, it is recommended that you include all three IP addresses in your allowlists.
Hyperproof EU IP addresses - 9.141.172.46, 4.185.45.100
Hyperproof Gov IP addresses - 4.155.77.155, 4.155.78.5, 4.155.8.97
See Hyperproof instances for more information.
Permissions
The permissions below need to be granted per user in each Jira project linked to Hyperproof.
Note: Ensure that each connected Jira project has a valid Default Assignee who has assignable user permission in the project. If the Default Assignee is unassigned, your Jira instance must have the Allow unassigned issues option enabled.
|
|
|
|
|
|
|
|
|
|
Tip: Hyperproof’s Jira Server task integration supports personal access tokens, allowing users to use Hyperproof's Jira integrations when Jira administrators have disabled basic authentication.