How to move work items from one project area to another in the same RTC 6.0.2 repository
Hello, We need to urgently move work items in one project area to another one in the same repository and retain their IDs, all links, history, attachments, attributes, etc. Both project areas are inheriting the same process. I saw that when you select one work item in the RTC Eclipse client there is an option to move it to another project area in the same repository. However we need to move thousands of work items and manually it would be virtually impossible to do it. Is there an "scm" command to use in a script? I know that there is a plug-in created for bulk move but it is not usable for our RTC version - 6.0.2. In general: what is the best option?
Thanks in advance for your support! |
2 answers
Krasimir,
your request is totally legitimite. Unfortunately it seems you are stuck in history between the (unsupported) bulk move plugin not being further updated and the actual feature request not being implemented yet. I suggest to subscribe to the feature request. To solve your actual problem you will need to write a java script against the RTC client SDK which changes the ownership of the work items. A good starting point is https://rsjazz.wordpress.com/2012/10/29/using-work-item-queris-for-automation/ - Arne |
Krasimir,
As discussed we now have a PlugIn that can move a work item with all references (change sets, approvals, comments, ...). So everything should be fine and we can proceed with the move of one team area within a project area to another project area on the same server.
Best regards
Alexander
Comments Hi Krasimir,
Was this resolved?
I am using RTC 5.0.2 and have a smiliare situation . I need to move some work items along with its children to another project without losing data and references. Can you let me know how you went about resolving this issue?
Stefan Oblinger
commented Sep 21 '18, 9:07 a.m.
This solution might help: |
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
Dear Colleagues,