Import WorkItems from CSV including parent/child links (RTC 4.0.2 and later)
In this video a CSV file is imported and as a result the work items have parent/child links.
How was this done?
import-work-item-and-the-links-from-csv-file points out to use
id,parent
1234,#1233
I understand how to use this to link new work items to existing work items (id attribute known), but was wondering how to use this when the ID of the parent is not known (RTC sets it to a unique number during import)
How was this done?
import-work-item-and-the-links-from-csv-file points out to use
id,parent
1234,#1233
I understand how to use this to link new work items to existing work items (id attribute known), but was wondering how to use this when the ID of the parent is not known (RTC sets it to a unique number during import)
Accepted answer
The answer is simple: RTC is smart
RTC is able to use any ID in the import file to determine the link to set, but use actual/real (new) IDs during import.
So here is a demo.csv:
Id,Type,Summary,Filed Against,Parent
1233,Task,aParent,aCategory
1234,Task,aChild,aCategory,#1233
RTC is able to use any ID in the import file to determine the link to set, but use actual/real (new) IDs during import.
So here is a demo.csv:
Id,Type,Summary,Filed Against,Parent
1233,Task,aParent,aCategory
1234,Task,aChild,aCategory,#1233
