This topic describes the process of importing data to TrackStudio from other issue tracking systems.
Open the created TrackStudio XML export 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
To import a task, create a record in the GR_TASK table. To import a user, create a record it the GR_USER table. 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.
4. Compare the file created at step 3 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.
To simplify installation we don't send license with embedded evaluation period by e-mail. Instead, TrackStudio estimates the evaluation period based on submit date of your tasks. This feature has a side effect: if you import tasks submitted more than 90 days ago you will got the License Exception during Login process. To workaround this issue set the task_submitdate to the current date for all your imported tasks. After purchase you can re-import those tasks with actual submit dates.