Problems Importing New Work Items from a CSV File with an Existing Parent Work Item in RTC 4.0.3
In RTC 4.0.3 using the 4.0.3 Eclipse client, when importing new work work items with included parent ids
from a CSV file, the actual parent ids assigned to the created work items are taken from the last line of the import file instead of the lines where the new work items are specified. This problem also exists for Eclipse client 3.0.1.6 and 4.0.2. It works correctly for Eclipse Client 3.0.1.2. What follows is an actual example: Here is the CSV import file: Id,Parent,Summary,Story ID,Type *,#268293,Development Review,150-405CL,Development Review *,#268293,Architect Review,150-405CL,Review *,#268293,QA Execution Team Review,150-405CL,QA Execution Team Review *,#268293,Conversion Review,150-405CL,Review *,#268293,DCS Review,150-405CL,DCS Review *,#268293,Batch Job Review,150-405CL,Batch Job Review *,#268277,Development Review,700-091CL,Development Review *,#268277,Architect Review,700-091CL,Review *,#268277,QA Execution Team Review,700-091CL,QA Execution Team Review *,#268277,Conversion Review,700-091CL,Review *,#268277,DCS Review,700-091CL,DCS Review *,#268277,Batch Job Review,700-091CL,Batch Job Review *,#268327,Development Review,150-406CL,Development Review *,#268327,Architect Review,150-406CL,Review *,#268327,QA Execution Team Review,150-406CL,QA Execution Team Review *,#268327,Conversion Review,150-406CL,Review *,#268327,DCS Review,150-406CL,DCS Review *,#268327,Batch Job Review,150-406CL,Batch Job Review Here are the new work items imported into RTC 4.0.3 using 3.0.1.2 Eclipse Client and then exported to a CSV file. Id,Parent,Summary,Story ID,Type 283044,#268293,Development Review,150-405CL,Development Review 283045,#268293,Architect Review,150-405CL,Review 283046,#268293,QA Execution Team Review,150-405CL,QA Execution Team Review 283047,#268293,Conversion Review,150-405CL,Review 283048,#268293,DCS Review,150-405CL,DCS Review 283049,#268293,Batch Job Review,150-405CL,Batch Job Review 283050,#268277,Development Review,700-091CL,Development Review 283051,#268277,Architect Review,700-091CL,Review 283052,#268277,QA Execution Team Review,700-091CL,QA Execution Team Review 283053,#268277,Conversion Review,700-091CL,Review 283054,#268277,DCS Review,700-091CL,DCS Review 283055,#268277,Batch Job Review,700-091CL,Batch Job Review 283056,#268327,Development Review,150-406CL,Development Review 283057,#268327,Architect Review,150-406CL,Review 283058,#268327,QA Execution Team Review,150-406CL,QA Execution Team Review 283059,#268327,Conversion Review,150-406CL,Review 283060,#268327,DCS Review,150-406CL,DCS Review 283061,#268327,Batch Job Review,150-406CL,Batch Job Review Here are the new work items imported into RTC 4.0.3 using 4.0.3 Eclipse Client and then exported to a CSV file. Id,Parent,Summary,Story ID,Type 283062,#268327,Development Review,150-405CL,Development Review 283063,#268327,Architect Review,150-405CL,Review 283064,#268327,QA Execution Team Review,150-405CL,QA Execution Team Review 283065,#268327,Conversion Review,150-405CL,Review 283066,#268327,DCS Review,150-405CL,DCS Review 283067,#268327,Batch Job Review,150-405CL,Batch Job Review 283074,#268327,Development Review,150-406CL,Development Review 283075,#268327,Architect Review,150-406CL,Review 283076,#268327,QA Execution Team Review,150-406CL,QA Execution Team Review 283077,#268327,Conversion Review,150-406CL,Review 283078,#268327,DCS Review,150-406CL,DCS Review 283079,#268327,Batch Job Review,150-406CL,Batch Job Review 283068,#268327,Development Review,700-091CL,Development Review 283069,#268327,Architect Review,700-091CL,Review 283070,#268327,QA Execution Team Review,700-091CL,QA Execution Team Review 283071,#268327,Conversion Review,700-091CL,Review 283072,#268327,DCS Review,700-091CL,DCS Review 283073,#268327,Batch Job Review,700-091CL,Batch Job Review |
2 answers
I just got the same issue today. And I found the problem is only happened if the csv file contains "ID" column but the content of the column is empty.
The issue can be fixed after removing the ID column if you only need to create new work item from a csv file. Hope the solution is helpful to others who experience the same issue. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Hi Robert,
I don't have the issue in RTC 4.0.3 server and 4.0.3 client environment. During the import, did you use any custom mapping file?
No custom mapping. Also, let me emphasize that it works fine to import parent links to existing work items. It is only a problem when new work items are being created with parent links to existing work items.
I am pretty sure it is the same issues as this: https://jazz.net/forum/questions/102872/rtc-import-utility-using-csv-file-may-be-a-bug