i'm also trying to move work items, i'd like to move the whole project, from one repository to another, and was looking at the "RTC301SimpleProjectMove article mentioned - one main problem "LINKS". The big power of RTC and the other JAZZ based tools are the artifacts can all be linked together - but you loose all those links if you migrate - that's kind of stupid!

also, the article says you can preserve "change sets", which are just another kind of link, but it says you have to run a tool called "TAN" and when I click to find out, i get ACCESS DENIED.... here is what the article says:

"If you plan on re-creating the links between change sets and work items, ensure the tags and description are exported. Then install the Migration Assistant Plugin? into RTC, click on your query in the TAN and run Preserve Work Items for Export. "

SO, what is this MIGRATION ASSISTANT PLUGIN?? what is TAN??

why can't we actually move work items from one repository to another, with all the DATA?

ken

I was reviewing some of the articles and came across this one:
https://jazz.net/wiki/bin/view/Main/RTC301SimpleProjectMove

I was really interested in this because this is very similar to what I am trying to do right now. Whether it's moving items from a project area on the same server/repository or another server/repository, the steps seem to be the same to move it and merge it into an existing project area. However, there are some tools mentioned but not attached and the author's e-mail no longer works.

Does anyone know if there has been any further progress on such work? Or even if the tools are publicly available for testing?

Despite being able to move work items and source. My understanding is generally that there are the following limitations:
1. Any queries in the source project area will have to be re-created in the target project area.
2. Same with any dashboards.
3. Mentions of work item and attachment numbers in comments of work items being exported/imported will be incorrect due to new unique IDs if creating work items on a new target server.

Is my understanding correct? Or am I missing further options using the APIs somehow?

TAN is an abbreviation for "Team Artifacts Navigator", which is an
Eclipse view. To my knowledge, the "Migration Assistant Plug-in" is not
sufficiently developed to be used by anyone other than the development
team (if anyone knows otherwise, please follow-up with details).

Also note that this is a wiki entry, and as a reminder, the top of every
page of the wiki has the following highlighted note:

-----------
NOTE: The development wiki is a work area used by the Jazz development
teams to plan and discuss technical designs and operational procedures
related to the development projects at Jazz.net. Often you will find
work items linking to documents in the wiki. Everyone is welcome to
browse the wiki, follow along, and participate in the development
process. Participation is what Jazz.net is all about! But please keep in
mind that information on the wiki is "as is", unsupported, and may be
outdated or inaccurate. For information on released products, consult
the product documentation, support tech notes, and the Jazz.net library.
------------

See work item 93151 to track and/or comment on actual cross-repository
project area move support.

Cheers,
Geoff


On 9/29/2011 2:08 PM, kcreager wrote:

i'm also trying to move work items, i'd like to move the whole
project, from one repository to another, and was looking at the
"RTC301SimpleProjectMove article mentioned - one main problem
"LINKS". The big power of RTC and the other JAZZ based
tools are the artifacts can all be linked together - but you loose
all those links if you migrate - that's kind of stupid!

also, the article says you can preserve "change sets", which
are just another kind of link, but it says you have to run a tool
called "TAN" and when I click to find out, i get ACCESS
DENIED.... here is what the article says:

"If you plan on re-creating the links between change sets and
work items, ensure the tags and description are exported. Then
install the Migration Assistant Plugin? into RTC, click on your query
in the TAN and run Preserve Work Items for Export. "

SO, what is this MIGRATION ASSISTANT PLUGIN?? what is TAN??

why can't we actually move work items from one repository to another,
with all the DATA?

ken


piperpwrote:
I was reviewing some of the articles and came across this one:
https://jazz.net/wiki/bin/view/Main/RTC301SimpleProjectMove

I was really interested in this because this is very similar to what
I am trying to do right now. Whether it's moving items from a project
area on the same server/repository or another server/repository, the
steps seem to be the same to move it and merge it into an existing
project area. However, there are some tools mentioned but not
attached and the author's e-mail no longer works.

Does anyone know if there has been any further progress on such
work? Or even if the tools are publicly available for testing?

Despite being able to move work items and source. My understanding
is generally that there are the following limitations:
1. Any queries in the source project area will have to be re-created
in the target project area.
2. Same with any dashboards.
3. Mentions of work item and attachment numbers in comments of work
items being exported/imported will be incorrect due to new unique IDs
if creating work items on a new target server.

Is my understanding correct? Or am I missing further options using
the APIs somehow?