TrackStudio 3.0 Documentation
Importing from Other Systems

This topic describes the process of importing data to TrackStudio from other issue tracking systems.

To import data from other systems using the database import/export feature in TrackStudio Enterprise Server Manager (available in TrackStudio/SA): 

1. Export to XML the original database to which the data will be imported afterwards. To do it, launch sman.exe, switch to the Database Management tab, enter a name for the output file and press the Export Database button. If there is no original database, create and initialize a database first. 

2. Open the created XML file using any XML editor or text editor. 

The XML file looks as follows:

<tsExportData>
  <table name="TABLENAME">
    <row>
      <data name="COLUMNNAME1"><![CDATA[DATA1]]></data>
      <data name="COLUMNNAME2"><![CDATA[DATA2]]></data>
      ...
    </row>
    ...
  </table>
  ...
</tsExportData>

Where 

 

  • TABLENAME -- the name of a table in the database
  • COLUMNNAMEi -- the name of a column in the current database
  • DATAi -- the values of table fields for the current record

 

3. Export the data from the old issue tracking system into TrackStudio XML file. For instance, to import a task, you need to create a record in the GR_TASK table, while to import a user, you will need a record it in the GR_USER. Then add records with user and task descriptions to the XML file created in step 1. 

4. Use the XML file created in step 2 to initialize a database. To do it, launch sman.exe, switch to the Database Management tab, specify the name of the XML file and press the Create Database button.

To find out what tables should be modified to create an object: 

1. Export the database. 

2. Log into TrackStudio and create the needed object using the web interface (workflow, message, etc). 

3. Export the database once again and compare the newly created file with the file created at step 1.

Each record has a unique primary key, for example task_id, user_id. TrackStudio uses the GUID generator to set the value of the primary key. When importing data, you can use any method to define the primary key-- just take care that the record keys are unique for each table. The maximum key length is 32 bytes. 

 

Copyright (c) 2002-2004. TrackStudio, Ltd. All rights reserved.