Import and export risks

Modified on Fri, 11 Sep at 7:56 AM

You can import risks in bulk using an Excel template, and export issue views or individual risks. This article shows you how both work.


Prerequisites for import

  • You are an owner of the team – only owners can import risks
  • The file is in .xlsx format and no larger than 3 MB


Import risks

  1. Open your team's Team details.
  2. Click Import issuesin the three-dot menu.

  3. Fill in the risk import templatefrom the attachment, then select the file or drag it into the upload field.

  4. Click Import.
Important: The import only supports plain text. Formatting, links, formulas, and images are not carried over.
Important: For Responsible and Editor, the usernames in the Excel file must be entirely lowercase. These users won't automatically become members of the team – add them manually afterward if needed.

If an error occurs during import, none of the data from the Excel file is applied. In this case, check the error message shown and correct the file accordingly.

Good to know: Import is currently only available for risks, not for opportunities.


Export risks

Export an issue view

  1. Open the view you want to export, for example All issues.
  2. Click the three-dot menu in the top right and select Export as Excel file.

The export contains exactly the columns, sorting, and filter currently set in the view. Issue descriptions aren't included, and priority and issue type are shown as text instead of icons. Clicking the issue ID in the exported file takes you directly to that issue, provided you have access to it.

Export a single risk

  1. Open the risk you want to export.
  2. Click the three-dot menu in the top right and select Print.

The risk is exported as a PDF with all its information.


Related articles

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article