Roles and permissions
The following roles can create a Jira issue via Hyperproof:
Anyone with manager or contributor permissions on the task
Note: To use Jira with Hyperproof, your Hyperproof administrator must first configure the integration. See Connecting Hyperproof to Jira Cloud and Connecting Hyperproof to Jira Server
From the left menu, select the tab that corresponds to the object you want to link the task to. For example, if you want to link the task to a control, select the Controls tab.
Select the specific object. For example, if you want the task linked to control ID 1234, select that control.
Click the Task icon.
Optionally, click the Pin icon to pin the Tasks panel.
Click New task.
If this is your first time using the Jira integration, follow the steps below. If you’ve already signed in to Jira in Hyperproof, skip to the next step.
In the task's left pane, click the Jira integration icon.
The Authorize app window opens.
Click Accept.
The Authorize Hyperproof window opens.
Click Allow.
Click the Jira integration icon, then select Create a new issue from this task.
Select your options from the drop-down menus. Note that menus with asterisks (*) are required fields.
Data synced between Hyperproof and Jira is dependent on the Jira project. When creating or syncing issues, the integration fetches the available fields for the specific project and issue type using the Jira API. This ensures that only the fields relevant to the selected Jira project and issue type are presented and processed. The available fields (including custom fields) can vary between projects due to Jira's project-level configuration.
Enter a name for the task. This field is required. Task titles have a 250-character limit.
Enter a description.
The Assign by defaults to Individual. There is no Group option for Jira tasks.
In Jira Server assignee select an assignee from the drop-down menu.
Note: Select Unassigned to leave the task unassigned.
In the Due date field, enter the date this task should be completed.
In the Priority field, select a priority setting for this task.
The Target field can't be edited during task creation unless you are creating the task from the Work items > Tasks tab. It should display the object ID of the object where you are adding a task, such as a Control ID.
The proof field can't be edited during task creation.
Note: Proof cannot be linked until the task is created. When proof is uploaded, it's linked to the task and is visible in the task's proof area. The proof remains linked to the task until the task is submitted and closed. Note that if there are several pieces of proof linked to the task, you may need to use the scroll bar to view all of the proof.
If the task has an approval configured, proof isn't attached to linked objects until the proof is approved, and the task is submitted and closed.
When the task is closed, the proof can be found in the task's proof area, the linked object's Proof tab (e.g., the Proof tab of a control), and the organization's main proof list. This activity can be observed in the task's Activity Feed.
Click Create.
The task is created.
Troubleshooting
Time out error
If you receive a timeout error while attempting to create a Jira issue in Hyperproof, it’s more than likely due to your Hyperproof connection remaining open for an extended period of time. To resolve this issue, follow the steps below.
From the left menu, select Settings.
Select Connected accounts.
From the list of connections, select your Jira connection.
Click the ... (More options) icon, then select Disconnect.
Navigate back to the task, then click the Jira integration icon.
Select Create a new issue from this task. Follow steps 4 and 5 in the previous section.
Error creating the task
If you receive an error when creating the task, the issue could be due to a required Jira field not being completed. If the required field is not of a supported field type, you may not be able to fill it in from the Hyperproof task window, which will generate an error. Work with your Jira administrator to change the field type or make the field not required. See Supported Jira custom fields.
