You can use the XML Import/Export feature to migrate your existing artifact database into a new Project Tracker database. You can also use this feature to synchronize your older or external tracking component database with the Project Tracker database. This allows you to continue using the older tracking component until your project's members are comfortable with Project Tracker. Once the import is completed, you can treat the imported artifacts just like any other Project Tracker artifact.
This feature exports artifacts as XML which you can either view in the browser window or save as a downloadable file. You can use the exported file for a variety of purposes, such as archiving artifacts or synchronizing other tracking databases with the Project Tracker database. Artifacts may be exported from the current project only. You must have the Project Artifact Tracking - Query permission to use the XML export artifacts feature.
You can export artifacts singly or in batches. When exporting batches of artifacts, you can include artifacts by including their IDs in a comma-separated list or a range of IDs. Specifying a comma-separated list exports only the artifacts specified in the list. For example, 10, 20, 30, 50 will export only artifacts 10, 20, 30 and 50. Specifying a range of artifact IDs exports all artifacts in the range. For example, 1-50 will export all artifacts with IDs from 1 to 50. You can specify artifacts to export using a combination of comma-separated list and ranges. For example: 1-5, 10, 20 will export artifacts 1 through 5 and artifacts 10 and 20. A Namespace title element is always generated in the exported XML file.
To export artifacts:
This feature imports artifact data from XML files. The imported artifacts are treated as new artifacts in the Project Tracker database. You must have the Project Issue Tracking - Submit permission to use the XML import artifacts feature.
Project Tracker accepts only those XML files that follow the Project Tracker Document Type Definition (DTD). The following elements in the "project" section of the XML file must match the settings for the current project:
<domain>domain.com</domain>.<name>project</name>.<code>SC</code>.<namespace-title>DEFAULT</namespace-title>.The project to which you are importing must contain all of the usernames, artifact types, attributes, attribute options and Namespace titles referenced in the XML file. On a successful import, Project Tracker creates a new artifact for each artifact in the XML file and assigns an artifact ID to each. You can then treat these new artifacts as you would any other artifact in the database.
Even if you do not specify a Namespace title in the Namespace element in the XML file, the import will still be successful. Here, Project Tracker will associate the default domain Namespace title to the each imported artifact type and attribute. For example, if you exported artifact "SC1" which has the "IT to PT conversion" Namespace title associated to it, the XML file will contain the <namespace-title>IT to PT conversion</namespace-title> tag for artifact "SC1." Now, if you remove the Namespace title in this file, and import it once again, Project Tracker will take the default domain Namespace name, that is "DEFAULT".
But, if you try import an XML file without the "<namespace-title>namespace name<namespace-title>" tag, or change the Namespace title name to an ambiguous name, you will receive an error.
Once the import is complete, you will receive a log detailing the results of the import. If the import completes in 30 seconds or less, the import results are displayed on the screen. For larger imports which take longer than 30 seconds to complete, the import results are emailed to you.
To import artifacts:
You can write scripts which will run Project Tracker queries or reports, automating execution of saved queries and reports that you wish to run regularly. More information about this can be found in Using scripts to run queries and reports