What are the steps and pre-requisites for moving work items cross server and cross project area?
![]()
Hello!
I have two RTC 3.0.1.1 installations on two separate servers with two identical project areas (based off of the same process template). Since I am decommissioning one I need to move the work items to the new server. I have explored various possibilities (DB migration, export/import functionality) but have not managed to satisfy all of my requirements. I am currently evaluating the possibility of using the move/copy functionality to transfer work items between project areas. What are the pre-requisites/steps for doing this? I have found this link: https://jazz.net/wiki/bin/view/Main/BulkMoveWorkItemsBetweenProjectAreasInRTC3, but it is for RTC 3.0.1.3, and I was going to use the web interface for doing so (although I supposed the Eclipse client would work as well) by clicking the move/copy button and selecting the target project area. What are the connections that I have to establish between project areas (on separate servers) under the server configuration? Once I have done this, will the move/copy functionality copy history and attachments as well? Thank you and best regards, Andrew |
One answer
![]()
there is no function to move history. there is no function to deal with the changed workitem numbers on the other server, there is no function to deal with the attachments and urls of same.
this function is not supported, nor is there any code that 'works'. we have built a tool that does most of the work, ~95%.. there is manual touchup on almost every workitem . we use pentaho as our base etl tool. Comments Hello Sam,
No, sorry, it is not. Just letting you know that we had to create our own as IBM is as yet unable to provide this function.
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
It is actually possible to create a work item with a specific ID, provided that it is not yet used.
well, if history is important enough to create, it will be important enough to move.
|
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.