It's all about the answers!

Ask a question

Moving CLM artifacts from one project area to another with a different RTC project template

Liora Milbaum (513282117) | asked Apr 27 '14, 2:55 a.m.

A customer has deployed CLM 4.0.4 using customized Agile process template (for RTC).  Now, he wants to switch to Agile ALM process template. More then that, he wants to split one huge project area to multiple project areas.

What would be the best approach to accomplish this task?

Would appreciate you feedback and insights,

sam detweiler commented Apr 27 '14, 6:43 a.m.

what is the Agile ALM template? 

anyhow, the best way to move workitems from one project to another is to export then import with a mapping file to to get the fields adjusted to the new workitem data layout.  but export/import doesn't do everything.. attachments, approvals, and links are not handled.

but all the rest of the data timelines, users, team areas, categories, plans, and build info have to be copied manually.

on my last job we had to write a set of utilities to do all this.

Liora Milbaum commented Apr 27 '14, 7:03 a.m.
Hi Sam,

Thanks for sharing.

Agile ALM process template - 

We want to move not only workitems but requirements and test artifacts as well. The client is using RTC, RQM and RRC.
Using export and import won't work as we have lots of links between the artifacts. There is no way we can handle it manually.

Which API did you use for the set of utilities mentioned? We are looking into OSLC.

Thanks again,

sam detweiler commented Apr 27 '14, 7:25 a.m.

there are no tools provided to do what you want.

much of the data you want to copy is not available thru OSLC or REST apis, so we built ours on the java client api, sometimes being forced to use internal functions to get the job done.

it was a couple months of 2 people working on it.. one to do the project area structure as I mentioned above, and one to do the extra data in workitems.
find all the links and fix them up with their new workitem numbers, same for attachments..  we did not fixup referenced workitems in source changesets.

we also had the need to move these projects across servers. so we were sure the artifact ID's were different.

the intent was that the team shouldn't have to do anything differently but use a different project area on Monday than they did on Friday when they went home.

this was RTC only.. I have no idea personally what you would need to do for RRC/RQM artifacts.

the need to split presents some additional challenges. (we were merging RTC projects together, which was hard enough).

sam detweiler commented Apr 27 '14, 7:33 a.m.

in my opinion the Bulk workitem Move tool doesn't handle different process template issues.

Accepted answer

permanent link
Liora Milbaum (513282117) | answered Apr 27 '14, 11:08 p.m.

Thanks for the valuable info.  We are reconsidering our strategy in light of the info you provided. Maybe, it is preferable using repotools to import all data from the current CLM server. The artifacts created till now will be stored in the current project area and all the new work/artifacts will be stored in the new project areas.


Geoffrey Clemm selected this answer as the correct answer

Your answer

Register or to post your answer.