Import, Export, and Bulk Operations
Use import/export for reporting, backup-style snapshots, and migration between projects. Bulk operations help you manage multiple risks efficiently.
Export risks to CSV
Export your risk register for external reporting, backup, or analysis.
Export options
From the app header, click Export and choose:
| Option | Description |
|---|---|
| Export All Risks | Downloads all risks in the project |
| Export Filtered Risks | Downloads only risks matching current filters |
CSV format
The exported CSV includes these columns:
| Column | Description |
|---|---|
ID | Unique risk identifier |
Title | Risk name |
Description | Detailed description |
Status | Open, Mitigated, or Closed |
Probability | 1-5 value |
Impact | 1-5 value |
Score | Calculated (Probability × Impact) |
Owner | Display name of assigned user |
Mitigation | Mitigation plan text |
Created At | ISO timestamp |
Created By | Display name of creator |
Export use cases
- Stakeholder reporting: Share risk status with leadership
- Backup: Create periodic snapshots of your risk register
- Analysis: Import into spreadsheets for charts and analysis
- Migration: Move risks to another project or system
Import risks from CSV
Import risks from a CSV file to bulk-create risks or migrate from other systems.
Import process
- Click Import CSV in the app header
- Select a
.csvfile from your computer - Review the import results:
- Count of successfully imported risks
- Any validation errors for failed rows
Recommended workflow
For best results:
- Export first: Use an export from this app as your template
- Keep structure: Maintain column headers and order
- Add data: Add your new risks below the existing rows
- Import: Upload the modified file
Required columns
Your CSV must include these headers (case-sensitive):
| Column | Required | Validation |
|---|---|---|
Title | Yes | Max 200 characters |
Description | Yes | Max 1000 characters |
Status | Yes | Must be: open, mitigated, or closed |
Probability | Yes | Must be: 1, 2, 3, 4, or 5 |
Impact | Yes | Must be: 1, 2, 3, 4, or 5 |
Mitigation | Yes | Max 1000 characters |
Optional columns
| Column | Notes |
|---|---|
ID | Ignored during import (new IDs are generated) |
Score | Ignored (calculated from Probability × Impact) |
Owner | If provided, must match a project user’s display name |
Created At | Ignored (current timestamp used) |
Created By | Ignored (current user used) |
Validation rules
During import, each row is validated:
| Field | Rule |
|---|---|
| Title | Required, ≤200 characters |
| Description | ≤1000 characters |
| Status | Must be: open, mitigated, closed |
| Probability | Must be: 1, 2, 3, 4, 5 |
| Impact | Must be: 1, 2, 3, 4, 5 |
| Mitigation | ≤1000 characters |
Rows that fail validation are skipped. Errors are reported with row numbers.
Import tips
- Start fresh: Don’t include the ID column - new IDs are generated
- Match owners exactly: Owner names must match project user names exactly
- Check status values: Use lowercase:
open,mitigated,closed - Number values: Probability and Impact must be numbers, not text
Bulk operations in table view
When multiple risks are selected, use bulk actions to update them all at once.
Selecting risks for bulk operations
- Switch to Table view
- Click checkboxes to select individual risks
- Or click the header checkbox to select all visible risks
- The bulk action bar appears at the top
Available bulk actions
| Action | What it does |
|---|---|
| Set Probability | Updates probability (1-5) for all selected risks |
| Set Impact | Updates impact (1-5) for all selected risks |
| Set Status | Changes status for all selected risks |
| Set Owner | Reassigns owner for all selected risks |
| Delete | Removes all selected risks (requires confirmation) |
| Copy as Markdown | Copies selected risks to clipboard |
Bulk update workflow
- Select the risks you want to update
- Click the action button (e.g., “Set Status”)
- Choose the new value
- All selected risks are updated immediately
- Changes are logged in each risk’s history
Copy as Markdown
The Copy action creates formatted markdown text of selected risks:
## Selected Risks (3)
### Risk 1: Server capacity insufficient
- **Score:** 20 (Critical)
- **Status:** Open
- **Owner:** Jane Smith
- **Probability:** 4 | **Impact:** 5
### Risk 2: Third-party API downtime
...Use this for:
- Pasting into Confluence pages
- Sharing in Slack/Teams messages
- Including in email reports
- Creating documentation
When to use bulk operations
| Scenario | Bulk Action |
|---|---|
| After review meeting | Set Status to Mitigated for addressed risks |
| Reassigning ownership | Set Owner for risks changing hands |
| Risk reassessment | Set Probability or Impact after analysis |
| Cleanup | Delete stale or duplicate risks |
| Reporting | Copy risks for external documentation |
Best practices
For export
- Regular exports: Export monthly for backup and governance
- Use filters: Export filtered views for specific stakeholder needs
- Version exports: Name files with dates for historical tracking
For import
- Template approach: Export first, modify, then import
- Small batches: Start with a few rows to validate format
- Review errors: Check import results for validation issues
For bulk operations
- Review before acting: Verify your selection before bulk updates
- Use filters first: Filter to the right set, then select all
- One field at a time: Update one field per bulk action for clarity