Azure DevOps CSV import checker
Paste or open a CSV before you import it into Azure Boards (Boards > Queries > Import work items) or Test Plans. The checker lists the problems that make the import fail or silently drop values, per row and column. Free, no sign-in, nothing uploaded.
Your file never leaves your browser. Nothing is uploaded. The checker runs as a script on this page and makes no network requests with your data.
What it checks
The checker reads the file the way a CSV parser does and then looks at the values. It does not change your file.
The file itself
- Quoted values, line breaks inside quotes, and a quote that is never closed.
- Rows with more or fewer values than the header.
- A semicolon or tab delimiter instead of commas (common when Excel uses European regional settings).
- Characters that suggest the file is not saved as UTF-8.
- Empty or duplicate column names, and read-only columns such as Created By or Revision.
Boards: Import work items
- A missing Work Item Type or Title column, and new rows without a type or a title.
- IDs that are not whole numbers, IDs that appear twice, and titles longer than 255 characters.
- Work item types the CSV import does not support, such as Test Case or Test Plan.
- More than 1,000 rows in one file.
- A Parent column, which the import ignores, and Title 1, Title 2 ... columns that skip a level or have more than one title on a row.
- State or Reason on new work items, and Assigned To values without an email address.
- Work Item Type values with the wrong casing, such as user story or PBI.
Test Plans: Import test cases
- Missing columns: ID, Work Item Type, Title, Test Step, Step Action and Step Expected.
- A Work Item Type that is not exactly Test Case, and shared steps.
- Test Step values that are not whole numbers or are not numbered 1 to n within a test case.
- A State other than Design on a new test case, the usual cause of Invalid workitem field values found.
- Rows of one test case that have different values for the same field.
- A reminder that importing a test case with an ID replaces all of its steps.
Values in both
- Area Path and Iteration Path: forward slashes, a leading or trailing backslash, an Area or Iteration segment copied from the settings page, and different project names.
- Dates in a format that depends on the locale, or that are not dates.
- Numbers with a decimal comma or with text, and a Priority outside 1 to 4.
- Line breaks in HTML fields such as Description, and tags separated by commas instead of semicolons.
- Excel leftovers: scientific notation, #N/A and other error values, a leading apostrophe, and spaces around values.
What it can't check
The checker doesn't know your process, your area and iteration paths, your users, or the allowed values of your pick lists. Azure DevOps validates those when it saves the work item. A file without findings can therefore still be refused, so try a few rows in a test project first.
Minimal CSV that works
Boards: new work items with a hierarchy. The ID is empty, the type is on every row, and each child title is one column to the right of its parent, on the row below it.
ID,Work Item Type,Title 1,Title 2
,Epic,Online checkout,
,Feature,,Pay by card
,Feature,,Pay by invoice
Test Plans: new test cases with one row per step. The title is on the first row of a test case.
ID,Work Item Type,Title,Test Step,Step Action,Step Expected
,Test Case,Sign in with a valid account,1,Open the sign-in page,The page shows the form
,,,2,Enter a valid user name and password,The Sign in button is enabled
,,,3,Select Sign in,The dashboard is shown
Sources
- Import or update work items in bulk by using CSV files (Microsoft Learn)
- Bulk import or export test cases (Microsoft Learn)
- Test case import error: Invalid workitem field values found (our guide)
Install from the Marketplace See how it works