Download csv file c#

You can perform bulk import and export of work items using a CSV formatted file. While you can continue to use Excel for bulk import and updates, you can use the native import/export feature that doesn't require Excel. To learn more about using Excel, see Bulk add or modify work items with Excel.

You can perform bulk export of work items using a CSV formatted file. While you can continue to use Excel for bulk import and updates, you can use the native export feature from Queries that doesn't require Excel. To learn more about using Excel, see Bulk add or modify work items with Excel.

Note

The export feature is available with Azure DevOps Server 2019 Update 1 and later versions. The import feature is available with Azure DevOps Server 2020 and Azure DevOps Services.

Import new work items

All work items you import are created in a new state. This rule means that you can't specify field values that don't meet the field rules for the new state. For example, when you create a new user story with the Agile process, the State=New and the Reason=New. No other values can be specified.

1. Create a local import.csv file and open it in Visual Studio Code or Excel.

2. The file must contain the Work Item Type and the Title fields. You can include other columns as needed. In the following example, we include the Priority field.

3. From the web portal for your project, open Boards>Queries and choose the Import Work Items option.

   

4. Select your CSV file and then choose Import.

   

5. The import process loads the imported work items into the queries view in an unsaved state. Verify the results are what you want. Choose Save Items to save the work items.

   

6. The system highlights those work items with data issues. You need to resolve the data issues before you can save the work items. In this example, an invalid value has been entered into the Priority field. Fix the data by opening the work item directly. Alternatively, use bulk edit to fix several work items with the same issue.

   

Update existing work items

1. To update work items, create a query that contains all the columns you want to export and possibly edit. Save your query and select Export to CSV to save the data.csv file to your local machine.

   

   The exported file should look similar to the following syntax:

1. Make the edits to your work items. Your CSV file must contain the ID, Work Item Type, Title, and State fields. Any additional fields you want to include are optional.

   In the following example we change several values on existing working items.

1. Save the file and import (see steps 4-6 from the previous import section.)

2. The results list with work items that contain value changes appear highlighted in bold. Choose Save Items to apply the changes.

   

3. Work items with data issues are highlighted in red and need to be resolved before you can save them. In this example, an invalid value appears in the Assigned To field. Fix the data by opening the work item directly. Alternatively, you can use bulk edit if you have many work items with the same issue.

   

Export list as CSV

From any query, you can export a list of work items as a comma-delimited list. Simply open the query, choose the actions icon, and choose Export to CSV.

Note

Requires Azure DevOps Server 2019 Update 1 or later version.

Q & A

Can I import new items and update existing items in the same CSV file?

Absolutely! Leave the ID field empty for any new work items. In the following example, the last entry for an Epic doesn't specify an ID.

Can I import a CSV file that have parent-child links?

Yes, you can add child work items by indenting title columns. The following example add three child Issues under the already defined Epic.

Here is a better visual in Excel

How do I know if my imported file has errors?

Any problems with the formatting of your CSV file appear in the Results page of the import view. You can't import the work items until the formatting and syntax is correct.

The work items results always lists the data errors found for individual work items. Fix each error either from the web portal, or in the CSV file and import again.