Hyperproof and Jira workflow

Below is a basic Hyperproof and Jira workflow.

A task is created and assigned, and then linked to Jira

When a task is created in Hyperproof, the task creator has the option to link the task to their organization's Jira instance. The task assignee then works on the issue in Jira. If the assignee has any questions, they can leave a comment on the Jira issue. Their comments are synced to Hyperproof where the task creator can view them and respond. If the task creator comments back, the comment is synced to Jira.

The assignee works on the task and attaches proof via Jira

When the task assignee feels that the task is complete, they attach proof via the Jira issue and then mark the task as Done by changing the Jira issue’s status to Completed. This changes the task’s status in Hyperproof to Submitted, i.e. the assignee believes the work is done and the task creator can now review and verify. Note that all status changes are recorded in the task's Activity Feed.

The proof attached to the Jira issue is automatically synced into the Hyperproof task for easy verification by the task creator.

The proof is reviewed and the task is closed

If the proof is sufficient, the task creator closes the Hyperproof task. Proof linked to the task appears in the Proof tab on the task’s target object. For example, if the task is linked to a control, the proof is viewable via that control's Proof tab.

If the proof is not sufficient, the task owner changes the Hyperproof task’s status back to In progress which then changes the linked Jira issue’s status to In progress. The assignee is then alerted that they have more work to do.

If the task creator cancels the task, the status of the Jira issue changes to Completed.