Importing issues
Roles and permissions
The following roles can import issues:
Administrator
Compliance managers
Users
Issues can be imported into Hyperproof via CSV. The steps below explain how to download the example template, edit it, and then import it into Hyperproof.
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
From the left menu, select Work items.
Select the Issues tab.
Click Import.
The Import issues window opens.
Click Download the example CSV.
Step Two: Editing the CSV
Replace the contents of the example CSV with your own issues. Be sure to follow the format of the example file and the instructions on the page, to ensure that your issues 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 | |
|---|---|
Key | Should contain an ID that's unique to your organization. This field is required. Do one of the following:
|
Summary | This field fully describes the work that needs to be done. It can be a multi-line string. This field is required. |
Source type | The object the issue is linked to. This field is required. An issue can be linked to the following objects: Audit, Program, Control, Evaluation, Label, Request, Requirement, Risk, Risk Register, Vendor, and Vendor Register. Tip: Be sure to keep the object name singular so the field is not skipped during the import process. |
Source ID | The ID of the object the issue is linked to. This field is required. For example, if the issue is linked to a control in your ETSI program, the source ID would look something like ETSI422-4.2.4. Additional source ID examples:
|
Description | This is the full definition of the issue. It can be a multi-line string. This is an optional field. |
Status | A field for tracking the status of the issue. This is an optional field. Tip: Hyperproof recognizes the following issue statuses: Not started, In progress, Remediated, and Accepted. If no status is provided, the status defaults to 'Not started'. Note that 'Closed' is not a supported status. |
Action plan | A field for details on the agreed upon action plan to resolve the issue. This is an optional field. |
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 issue is assigned to the individual who imports the CSV. Additional tip: The assignee's email address must match the email address they use to sign in to Hyperproof. |
Due date | The date the issue needs to be completed. This is an optional field. NoteDates 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. |
Impact | A field for the impact the issue will have on your organization if it's not resolved. Hyperproof recognizes the following values: Highest, High, Medium, Low, and Lowest. This is an optional field. |
Effort level | A field for tracking how much work it will take to resolve the issue. Hyperproof recognizes the following values: Highest, High, Medium, Low, and Lowest. This is an optional field. This is an optional field. |
Priority | A field for prioritizing the issue. Hyperproof recognizes the following values: Highest, High, Medium, Low, and Lowest. This is an optional field. |
Business owner | The individual who owns the issue. Must be formatted as FirstName LastName (email address), i.e. Jennifer Cook (jcook@lunabtechnologies.org). This is an optional field. Tip: The assignee's email address must match the email address they use to sign in to Hyperproof. |
Executive sponsor | The individual who is of senior level and responsible for overseeing the remediation of the issue. Must be formatted as FirstName LastName (email address), i.e. Jennifer Cook (jcook@lunabtechnologies.org). This is an optional field. Tip: The assignee's email address must match the email address they use to sign in to Hyperproof. |
Discovered on | The date the issue was discovered. This is an optional field. NoteDates 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. |
Closed on | The date the issue was resolved. This is an optional field. NoteDates 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. |
Affected controls | A field for control IDs affected by the issue, e.g. ETSI422-4.2.4. This is an optional field. |
Affected labels | A field for labels affected by the issue, e.g. Code of Ethics. This is an optional field. |
Affected programs | A field for programs affected by the issue, e.g. Luna B.'s ETSI Program. This is an optional field. |
Affected audits | A field for audits affected by the issue, e.g. Quarterly Audit 2023. This is an optional field. |
Affected requests | A field for request IDs affected by the issue, e.g. R-14. This is an optional field. |
Affected requirements | A field for requirement IDs affected by the issue, e.g. 4.1.2 in [NAME OF PROGRAM]. This is an optional field. |
Affected risk registers | A field for the name of a risk register affected by the issue, e.g. Luna B.'s first risk register. This is an optional field. |
Affected vendor registers | A field for linking an issue to the vendor register. The value is Vendor. This is an optional field. |
Affected risks | A field for risk IDs affected by the issue, e.g. R-AC-2. This is an optional field. |
Affected vendors | A field for vendors affected by the issue, e.g. Galactacore. This is an optional field. |
Affected evaluations | A field for evaluation IDs affected by the issue, e.g. EVAL-52. This is an optional field. |
Custom fields |
Below is a snippet of a sample import file.
Step Three: Importing the CSV
After you’ve made the necessary changes to the CSV, it can be imported 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 should 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.