Hello cargne80,

One possible option would be to wait for 2.0 and use the CSV import capabilities.
Assuming you have your old work items in RTC already you could export them.
This would also allow some mapping from old to new attributes.

Another way I think would be possible is to make your old work items available
in a project on a different e.g. test server and then to move or copy them
into your new project area.
This can be done in a work item query. Select the work item to move/copy,
right click and select the context menu entry "Copy/Move to project area".
Unfortunately it only works for one work item at a time.

Ralph

I'm continuing with newbie questions.

I've built a personalized work item and workflow based on the
structure of my old work items. Now I want to import these old work
items that are saved on DB2 database.

I see that there is the opportunity to use bugzilla for this purpose,
but I also see that the DB2 database isn't supported from bugzilla.

Can I found a way to import my old work items in RTC?

Thanks in advance.

Hello cargne80,

I am confused.

Scenarios I can see: RTC 1.x

1.You have an older RTC installation, perhaps express c. You have work items
there. You created a new standard server and customized the workflows.
1.a You want to migrate the workitems from the old project into the new project.
This should be possible in simply bringing up your old server (maybe with
a different port) if you run on the same machine. The only way to migrate
the work items is to connect to both repositories from a client. Query all
work items one by one and use the move context menu entry to move then one
by one to the new project with the new process.
1.b Migrate the whole repository. Check the upgrade scenarios in the help.
However, that won't keep the new process. I'd create a process template from
you new process and after migrating the whole project try to paste the process
XML over the old XML to get it back. I'd suggest to try and test it before
you go into production. I'd set up a test server on some machine to explore
what works for you.

I don't know any other ways to migrate. You can check the export and import
capabilities of the Eclipse client but in 1.0 there were only export to CSV
files from queries but no import.
You cluld export and import change sets, but not both directions.

RTC 2.0beta
If you only want your work items from the old project you could export them
to a CSV file from a query and re import that file.

Maybe someone else can chime in?

Ralph

Perhaps I explain myself very bad.

I customize the structure of the work item in the standard edition.
Now I want to import my old system of protocols (with the same
functions of a work item) to the new system with work items in RTC.

Is this possible? My protocols are saved in a DB2 database and I see
that bugzilla doesn't support this type of database.

So, there is a method to import this data
?
Thanks very much.

Hello cargne80,

OK, got you. I'd suggest to write an exporter for your custom tool to generate
CSV (comma seperated value) tables and use the CSV work item importer then.
You couls also try to create a tool that queries your tool and generates
the work items in the new RTC server.
I don't see a way to just import the DB. My assumption is you would break
RTC.

Ralph

First of all thanks Ralph for your patience.

Perhaps my not native english language plus my first steps in RTC
don't permit me to explain well.

The scenario is: I don't use RTC 1.x

I use a my system, I builded myself, to report bug,task,...for the
projects.
And now I want to change system and to pass to RTC.
But I want to transfer my old bug,task,...into the work item
structure.

My old bug,task,...are saved in a DB2 database. Can I migrate these
old bug,task,...? (I've readed that I can't with bugzilla).

I hope now I explain myself.

Hello cargne80,

RTC 2.0 supports this (Beta2) File->Import

Type CSV and select the import underneath Team.

Hope his helps,

Ralph

rschoonwrote:

Hello cargne80,

OK, got you. I'd suggest to write an exporter for your custom tool

to generate

CSV (comma seperated value) tables and use the CSV work item

importer then.

You couls also try to create a tool that queries your tool and

generates

the work items in the new RTC server. I don't see a way to just
import the DB. My assumption is you would

break

RTC.

Ralph

Thanks for answer.
I've tried to generate csv tables from my tool, but now I don't found
anything in RTC that can import csv files. Possible?

Hello cargne80,

OK, got you. I'd suggest to write an exporter for your custom tool to generate
CSV (comma seperated value) tables and use the CSV work item importer then.
You couls also try to create a tool that queries your tool and generates
the work items in the new RTC server.
I don't see a way to just import the DB. My assumption is you would break
RTC.

Ralph

Thanks for answer.
I've tried to generate csv tables from my tool, but now I don't found anything in RTC that can import csv files. Possible?

EDIT: Ok, if I understand I need to convert my DB2 database in csv, then convert csv to XML's Bugzilla and then to import into RTC.
So: DB2 -> csv -> xml -> RTC

is this possible? or there is a less complicate manner?
If the system of migration is so complicated I continue to use my old tool. :roll:

Hi

To do the CSV import, you need to use RTC 2.0 (beta 2 is the latest version available). Then you can go DB2->CSV->RTC.

anthony