![Hyperproof.Io [Test] Help Center](https://downloads.intercomcdn.com/i/o/xgk1dxp2/757668/427b255f2659cc7e0853d6a00ec1/628914ae2617199b7d999ba797a5305a.png)
📝 Note
Hyperproof connects to many third-party systems that frequently change, including the system interface. Contact your System Administrator or the third-party provider for assistance in meeting the requirements to integrate with Hyperproof and collect the proof you need.
Hyperproof supports both Jira Server and Jira Data Center.
Create a Hypersync between Hyperproof and Jira to automatically collect proof from Jira. Jira proof types include:
Jira proof types and fields
Proof type | Fields | Testable |
Issue Details | This Hypersync proof shows information for the Jira issue in a similar format to what is shown in Jira itself. When a filter is selected, Hyperproof shows a list of available fields from the connected Jira instance. Optionally, users can select history fields to be included with the proof. | No |
List of Groups | Name, Members, Default, Product roles | Yes |
List of Issues | Fields on this proof type vary based on Jira settings. For more information, see Jira Cloud proof types. | Yes |
List of Users | Name, Email, Group, Active | Yes |
Additional documentation
📝 Note
You only need to connect Hyperproof to the app once, and then you can create as many Hypersyncs as you need.
Additionally, you can create multiple Hypersyncs for a single control or label.
Connection configuration
Authentication type: Custom
Custom authentication parameters: Jira Host URL, Username, Password
Certain cloud services offer specialized options for IP filtering in their cloud consoles to lock down specific cloud API endpoints for security and compliance purposes. You can use the Hyperproof static IP addresses to allow communication between Hyperproof Hypersyncs and your cloud service.
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.
📝 Note
IP addresses for the Hyperproof Gov will be deprecated and replaced, as shown in the following table:
Service | Current IP address | New IP address |
Main app | 4.154.201.6 | 4.155.77.155 |
Integrations | 4.246.104.90 | 4.155.78.5 |
To prevent connectivity issues, it is recommended that you include all four IP addresses in your allowlists.
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.154.201.6, 4.246.104.90
See Hyperproof instances for more information.
Hyperproof's Hypersync for Jira Server supports authentication using Personal Access Tokens in cases where your organization doesn't support basic authentication. The required authentication token can be found in Jira Server under Profile > Personal Access Tokens.
Filtering on the Issue Details and List of Issues proof types
Filtering in the Jira Hypersync is done by using Jira filters. This allows you to perform any kind of selection supported in Jira, as well as easily update the selection by changing the filter. The recommended best practice is to create a Jira filter that selects any issues (single or multiple) you're interested in.
Filters created in Jira need to be viewable by the user or service account using the Hypersync. The iterative development of the filter itself can be accomplished entirely in Jira, and can be edited/tested live until the record set is correct. Hyperproof then syncs the same record set once the filter is finalized.
Issue Details proof file names
File names for Issue Details proof files are generated automatically by Hyperproof based on the title of the Jira ticket. Instead of having an absolute maximum number of characters, Hyperproof truncates the file name at a logical point in the 160 to 180 character range based on the white space between the words in the title.
Requirements for the List of Users proof
To filter the List of Users proof type on a specific group, you must have the ADMINISTER (admin) permission in your Jira Data Center instance.
If you are using Jira Data Center, you must be at Jira Data Center version 11.
Including history fields for the Issue Details proof type
Additional history details can be included by selecting one or more history fields when configuring the Jira Hypersync. For example, selecting the Assignee history field includes the history of all changes to the assignee. Note that history fields are based on your organization's Jira configuration.
If your Jira Hypersync is already configured, you can add history fields via the Hypersync's settings. From the control or label, select the Automations tab and then locate the Hypersync. Hover over the Hypersync, and then click ... in the upper-right corner.
