Jira Server proof types

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.

See Hyperproof instances for more information.

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.

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.