Export/Import of Work Items - How to retain IDs?
Is there a way to export the work items from one RTC repository and import them to the new RTC repository and still retain the ID’s?
Thanks! |
6 answers
I wouldn't think so as the IDs start @ 1 and increase for each new work item created in the repository. I'd also wager the ID are immutable property in the back-end database, or at least a database generated value is stored. You're bound to hit clashes of ID quicker than you'd guess.
Kevin |
Can't we have a custom id field like in ClearQuest and increment the number on creation?
Comments
sam detweiler
commented Sep 05 '12, 7:37 a.m.
sure.. you can put anything in a custom field.. but the workitem base NUMBER will change.. retained to me is keep the workitem ID the same.. that cannot be done |
With some UUID manipulation can we retain the IDs? Just a thought!
Comments
Kevin Ramer
commented Sep 05 '12, 5:13 a.m.
I think your question has been answered. Anything else would be conjecture. |
Workaround (for the benefit of others): I had WIs with IDs from 124 to 925 on RTC server A. I had to move all the WIs to RTC server B with the same ID numbers. I created dummy WIs on RTC server B using dummy CSV file (dummy rows) with IDs from 1 to 925. Then I updated the WIs with the actual CSV file that I exported from RTC server A. So all of my WIs got updated and the dummy WIs (1 to 123) were moved to a different project and I will delete those WIs one a day :) |
interesting but only works ONCE if the server is new..
my servers are at workitems 117580 and 43865 adding adds to the end.. |
Is there a way to get "History" info when RTC WIs are exported/imported?
|
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
no.. IDs are NOT importable.. they are a generated value. (thus why moving data is so complicated)