Roles and permissions
The following roles can import repeating tasks:
Anyone can import repeating tasks linked to target objects where they are a member.
Tasks that repeat on a schedule or are triggered by an event can be imported into Hyperproof. Importing approval workflows as part of a repeating task is not supported.
Tip: Adding additional information does not overwrite existing data. During the import, Hyperproof searches for any exact data identifiers. If it doesn’t find any, it treats the data as new. If it finds a match, it updates the existing data.
Step One: Downloading the example CSV
The easiest way to start importing your own repeating tasks is by downloading Hyperproof’s example CSV. The example CSV provides the exact template for successfully importing repeating tasks into Hyperproof.
From the left menu, select Work items.
Select the Repeating tasks tab.
Click Import.
The Import repeating tasks window opens.
Click Download the example CSV.
Step Two: Editing the CSV
Replace the contents of the example CSV with your own repeating tasks. Be sure to follow the format of the example file, as well as the instructions on the page, to ensure that your repeating tasks can be successfully imported.
Note: The CSV must contain ALL headings listed below, even if they are optional. Keep in mind that headings are case-sensitive!
Heading |
|
Name | This is the name of the repeating task. This field is required.
Tip: Hyperproof supports up to 250 characters in the task title. |
Description | This is the full definition of the repeating task. It can be a multi-line string. This is an optional field.
The multi-line text limit for the description field is 65,535 characters. However, if you have a field with over 10,000 characters, it's highly recommended that you save the data in a document and link it as proof. |
Assignee | Must be formatted as FirstName LastName (email address), i.e., Jennifer Cook (jcook@lunabtechnologies.org). This is an optional field.
Tip: If no assignee is provided, the repeating task assignee is set to Unassigned.
Additional tip: The owner's email address must match the email address they use to sign in to Hyperproof. |
Group | The group assigned to the task. This is an optional field.
Tip: The group must already exist in your organization.
Additional tip: Ensure group names are spelled exactly as they are in Hyperproof. |
Organizer | The person who will be the owner of tasks created from this template or whose credentials will be used to create new tasks via a task integration. Must be formatted as FirstName LastName (email address), i.e., Jennifer Cook (jcook@lunabtechnologies.org). This is an optional field.
If no organizer is provided, the organizer defaults to the person importing the CSV. |
Target type | This is the object linked to the repeating task. This field is required.
Tip: A repeating task can be linked to the following objects: control, control scope, risk, and label. Be sure to keep the object name singular so the field is not skipped during import. |
Target identifier | The ID of the object linked to the repeating task. This field is required. For example, if the repeating task is linked to a control in your ETSI program, the target ID would look something like ETSI422-4.2.4. Additional target ID examples:
|
Repeats | Used to specify how the task repeats. Options:
This field is required. |
Repetition details | If you entered On schedule in the Repeats column, enter the interval in the Repetition details column. If you entered the interval directly in the Repeats column, you can leave this field blank. Intervals include:
If you entered On event in the Repeats column, enter the event that triggers the repeating task in the Repetition details column. Events include:
|
Event value | If you entered On an event in the Repeats column, use this field to specify what triggers the repeating task. Options include:
|
Starts on | A field for setting the date on which the task should begin repeating. If no date is specified, the field defaults to tomorrow. This is an optional field.
Note: Dates on imported records are parsed based on the date formats associated with your locale. If no valid date can be determined, Hyperproof displays an error. See Data interpreted by browser locale for a list of supported locales. |
Days until due | A field that specifies the number of days until the repeating task is due. This is an optional field.
Tip: This field defines the number of days in the future from the moment the repeating task is created. |
Priority | This is an optional field that lets you set the priority of the task created when the repeating task is triggered. Options:
|
Below is a sample import file.
Step Three: Importing the CSV
After you’ve made the necessary changes to the CSV, you can import it into Hyperproof.
Drag and drop the CSV file into the Upload CSV File field, or click Select file to upload to upload it manually.
Click Import.
Hyperproof checks the CSV to ensure that there are no errors. You’ll be alerted if Hyperproof encounters any errors.
If Hyperproof didn’t detect any errors, click Next. If Hyperproof detected errors, do one or both of the following:
First, use the Error viewer to identify the errors. Second, correct the errors directly in the CSV. This ensures that the CSV is up to date, if you need to re-import in the future.
Tip: Use the forward and backward arrows to cycle through the errors. The Error viewer gives specific information on what needs to be corrected.
Remove rows that contain errors by clicking Remove all rows with errors. Note that this doesn't remove any data in the actual CSV.
Click Next.
The CSV is imported.