Creating a Jira sub-task from a Hyperproof task
Roles and permissions
The following roles can create a Jira sub-task from a Hyperproof task:
- Anyone with manager or contributor permissions on the task 
- Limited access users cannot create a Jira sub-task 
This article explains how to create a Jira sub-task from a Hyperproof task. Note the following limitations:
- The parent issue for the sub-task must already exist in Jira. 
- If your Jira project does not expose sub-task issue types in the integration, you may need to adjust your Jira configuration. 
To create a Jira sub-task from a Hyperproof task:
- Create a new task. If you are unsure of how to create a task, refer to Creating a task. Note that Hyperproof task titles have a 250-character limit. 
- 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 step 3. - In the right pane of the task, 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. 
- Click Create. - The Jira sub-task is linked to the Hyperproof task.