Parent ID isn't getting applied to the User Story work items being bulk imported in Azure DevOps Feature

Question

Parent ID isn't getting applied to the User Story work items being bulk imported in Azure DevOps Feature

Answer 1

Hi Vishal,

You've encountered a common misunderstanding about how Azure DevOps handles parent-child relationships during CSV imports. The "Parent" field is a computed, read-only value in Azure DevOps — you can't directly set it by adding a column in your CSV file. When you import your spreadsheet, Azure DevOps ignores any Parent ID values you've entered.

CSV Import with Title Indentation

Azure DevOps CSV import supports parent-child links through Title column indentation (Title 1, Title 2, etc.) This is the officially recommended approach. Here's how:

CSV Format:

ID,Work Item Type,Title 1,Title 2,Assigned To,State,Priority
28,Feature,Feature A,,,Active,2
,User Story,,Story 1 under Feature,,New,1
,User Story,,Story 2 under Feature,,New,2
,User Story,,Story 3 under Feature,,New,2
,Feature,Imported Feature,,,To Do,2
,User Story,,Story 1 under New Feature,,New,1
,User Story,,Story 2 under New Feature,,New,2
,User Story,,Story 3 under New Feature,,New,2

Key Points:

• Title 1 column = Parent level (Feature)
• Title 2 column = Child level (User Stories)
• For new children, leave the ID column empty
• The parent Feature should have its ID specified (1545586)
• Children titles go in Title 2, NOT Title 1

Import Process:

1. Go to Boards → Queries → Import work items
2. Select your CSV file
3. Azure DevOps will automatically create the parent-child links based on the column indentation
4. Click Save Items

Answer 2

When importing work items from CSV via Boards → Queries → Import work items, only parent‑child links created by indenting Title columns are supported. Directly specifying a Parent ID column in the CSV is not applied.

Key behaviors and limitations from the CSV import feature:

1. The CSV must contain Work Item Type and Title. Other fields are allowed, but link types are restricted.
2. For parent‑child relationships, the supported method is to indent the Title columns to represent hierarchy. This is explicitly documented as the way to add parent‑child links when importing.
3. Other link types, including explicitly setting a Parent ID field, are not honored during CSV import. The system will import the work items but will not create the parent link from that field.

Because of this, the Parent ID values in the CSV are ignored and the imported User Stories appear without a parent in the query view.

To get the User Stories linked under a Feature, use one of these supported approaches:

1. Use CSV with hierarchy via Title indentation
   • Structure the CSV so that the parent item (e.g., Feature) appears above the children.
   • Use multiple Title columns (Title 1, Title 2, etc.) and indent the child rows under the parent as described in the documentation.
   • Import the CSV; Azure DevOps will create parent‑child links based on the indentation.
2. Use Excel integration with a tree list
   • Connect Excel to Azure DevOps and create a tree list (Epics → Features → User Stories).
   • Use Add Child and the Indent/Outdent item in tree actions to build the hierarchy.
   • Publish from Excel; Azure DevOps will create the parent‑child links automatically.
3. Create links after import
   • Import the User Stories without parent links.
   • Then use backlog mapping (drag‑and‑drop) or bulk edit in the web UI to link them to the desired Feature.

There is no supported way in this CSV import path to have the Parent ID column automatically create the parent link; the hierarchy must be expressed via Title indentation or managed after import.

---

References:

• Export, update, and import bulk work items with CSV files
• Add or modify work items in bulk with Microsoft Excel
• Tutorial: Organize your backlog and map child work items to parents in Azure Boards