Iterations are created upon CSV Import
Using RTC 4.0.1, I use the CSV Export / Import feature to update the "planned for" attribute for a couple of work items. I use this technote as a reference.
Here are the steps I follow: - create a query and use it to CSV export work items - add planned for attribute column, export as labels (default) - edit CSV file, change some values for the planned for attribute - CSV Import this file, chose to update work items I noticed that not found iterations are automatically created and corresponding work items have their planned for attribute value set to this newly created iteration, which is not what I expected. Is this a defect? |
One answer
|
Using labels to CSV Export / Import iteration attribute is not advisable as labels may not be unique withing the iterations / timelines hierarchy.
Example: you may have the following "backlog" iteration multiple times across iterations / timelines hierarchy. /Main Development/backlog /Maintenance/backlog The best way to handle iterations in the context of CSV Export and Import is to export iterations as id's (and not default labels). This ensures iterations uniqueness at import time. More information: work item 186356 work item 245730 work item 245729 Comments Additionally my enhancement request I did yesterday. The issue is very dangerous! You can simply create a mess. ouch. wish I had found this day before yesterday.. explains my timelines getting all messed up on 3.0.1.3 |
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.