![Hyperproof.Io [Test] Help Center](https://downloads.intercomcdn.com/i/o/xgk1dxp2/757668/427b255f2659cc7e0853d6a00ec1/628914ae2617199b7d999ba797a5305a.png)
👥 Roles and permissions
Only administrators can configure Jira for their organization
Hyperproof natively integrates with Jira, saving you time and increasing efficiency. The Jira integration is bidirectional, meaning it provides a two-way sync of Jira issues and Hyperproof tasks, which allows you to manage your work without disrupting your workflow. Note that proof uploaded in Jira can be uploaded to Hyperproof, but not vice versa.
📝 Note
Task synchronization from Jira to Hyperproof occurs every 5 minutes. Changes made to tasks in Hyperproof sync to Jira immediately.
📝 Note
If your Jira deployment changes from Jira Server or Jira Data Center to Jira Cloud, the integration stops working and all of your integrated tasks will need to be set up again, manually.
Connecting to Jira via Hyperproof
To use Jira with Hyperproof, your Hyperproof administrator must first configure the integration. The Jira integration is enabled in Hyperproof by default, however it must be configured to "fetch" your organization's Jira projects. Once it's configured, users can sign in to their Jira accounts via Hyperproof. See Connecting Hyperproof to Jira Cloud and Connecting Hyperproof to Jira Server
A note about comments on the Jira side
Comments posted to Jira are attributed to the Hyperproof user who created the Jira connection in Hyperproof. The correct commenter’s name still appears in italics beneath the comment within Jira, but the comment itself is technically posted using the integration creator’s credentials.
When a user connects Hyperproof to Jira, the integration uses that individual's Jira credentials for all actions taken through the connection. Because of this, Hyperproof can only post comments "as" the user who established the connection.
Data synchronized between Hyperproof and JIra tasks
When you configure a task integration between Hyperproof and Jira, the following task fields are always synced in both directions. If you make a change to one of these fields in Hyperproof, the change is sent to Jira. If you make a change to one of these fields in Jira, the change is sent to Hyperproof.
Task title
Task description
Assignee - Only single assignees are synchronized, not group assignees.
Status - See Jira status mapping, Connecting Hyperproof to Jira Cloud, Connecting Hyperproof to Jira Server for more information.
Comments - Comments made in Jira show in the Hyperproof task’s Activity Feed, and comments made in the Activity Feed show in Jira.
Proof sync is unilateral—from Jira to Hyperproof.
📝 Note
When you create a task in Hyperproof and save it, a corresponding issue is created in Jira. At that time, you can set the value of Jira custom fields, but they can't be changed from Hyperproof after the initial creation.
Synchronization schedule
Changes are synchronized as follows:
Changes made in Jira are synced to Hyperproof in two ways:
Every 5 minutes for tasks that have recently changed.
Once a night to update changes for all tasks.
Changes made in Hyperproof are synced to Jira immediately after an edit.