Importing Tasks
Got a spreadsheet full of tasks? Don’t create them one by one. Use CSV import to add them all at once.
When to use this
Section titled “When to use this”CSV import makes sense when you have:
- A long list of similar tasks (50 sites to inspect, 100 items on a checklist)
- Tasks from another system you want to bring into Valiro
- A template you use repeatedly for similar projects
If you’re just adding a handful of tasks, it’s probably faster to create them directly.
The process
Section titled “The process”- Create a CSV file with your tasks
- Upload it to Valiro
- Map the columns to Valiro fields
- Review and import
Setting up your CSV
Section titled “Setting up your CSV”At minimum, you need a title column. Everything else is optional but helpful.
title,description,assignee,dueDate,packageNameInspect Site #101,Safety and compliance check,john@company.com,2024-03-15,Assessment PhaseInspect Site #102,Safety and compliance check,john@company.com,2024-03-16,Assessment PhaseAvailable columns
Section titled “Available columns”- title (required) — What the task is called
- description — Details and instructions
- assignee — Email address of who should do it (must match a user in Valiro)
- status — “Not Started”, “In Progress”, “Completed”, or “Cancelled”
- priority — “High”, “Medium”, or “Low”
- dueDate — When it’s due (YYYY-MM-DD format works best)
- packageName — Which work package it belongs to (must match exactly)
Creating the file
Section titled “Creating the file”Use Excel, Google Sheets, or any spreadsheet app. When you’re done, export as CSV (usually File → Save As → CSV or File → Download → CSV).
Make sure dates are in a consistent format and emails match what’s in Valiro.
Common problems
Section titled “Common problems”“Assignee not found” — The email doesn’t match anyone in Valiro. Double-check spelling, or leave blank and assign later.
“Work package not found” — The package name doesn’t match exactly. Check capitalization and spelling. Create the work package first if it doesn’t exist.
“Invalid date” — Use YYYY-MM-DD format (2024-03-15) to avoid issues.
Test with a small sample first. Import 5-10 rows to make sure everything maps correctly, then do the full import.
Create work packages before importing. If your CSV references packages that don’t exist, the tasks might end up in the wrong place.
Keep your template. Once you have a CSV format that works, save it. You can reuse it for similar projects.
Related: Work Items for managing tasks after import. Work Packages for organizing tasks into phases.