Changes between Version 1 and Version 2 of TracImport


Ignore:
Timestamp:
09/26/06 13:01:24 (18 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracImport

    v1 v2  
    33== Bugzilla == 
    44 
    5 Ticket data can be imported from Bugzilla using the bugzilla2trac.py script, available in the contrib/ directory of the Trac distribution. 
     5Ticket data can be imported from Bugzilla using the [http://projects.edgewall.com/trac/browser/trunk/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the contrib/ directory of the Trac distribution. 
    66 
    77{{{ 
     
    2828  * bug activity (field changes) 
    2929  * bug attachments 
     30  * user names and passwords (put into a htpasswd file) 
    3031 
    3132The script provides a number of features to ease the conversion, such as: 
     
    4142== Sourceforge == 
    4243 
    43 Ticket data can be imported from Sourceforge using the sourceforge2trac.py script, available in the contrib/ directory of the Trac distribution. 
     44Ticket data can be imported from Sourceforge using the [http://projects.edgewall.com/trac/browser/trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution. 
     45 
     46== Mantis == 
     47 
     48Mantis bugs can be imported using the attached script. 
     49 
     50Currently, the following data is imported from Mantis: 
     51  * bugs 
     52  * bug comments 
     53  * bug activity (field changes) 
     54 
     55Attachments are NOT imported.  If you use the script, please read the NOTES section (at the top of the file) and make sure you adjust the config parameters for your environment. 
     56 
     57mantis2trac.py has the same parameters as the bugzilla2trac.py script: 
     58{{{ 
     59mantis2trac - Imports a bug database from Mantis into Trac. 
     60 
     61Usage: mantis2trac.py [options]  
     62 
     63Available Options: 
     64  --db <MySQL dbname>              - Mantis database 
     65  --tracenv /path/to/trac/env      - Full path to Trac db environment 
     66  -h | --host <MySQL hostname>     - Mantis DNS host name 
     67  -u | --user <MySQL username>     - Effective Mantis database user 
     68  -p | --passwd <MySQL password>   - Mantis database user password 
     69  -c | --clean                     - Remove current Trac tickets before importing 
     70  --help | help                    - This help info 
     71 
     72Additional configuration options can be defined directly in the script. 
     73}}}  
     74 
     75== Other == 
     76 
     77Since trac uses a SQL database to store the data, you can import from other systems by examining the database tables. Just go into [http://www.sqlite.org/sqlite.html sqlite] command line to look at the tables and import into them from your application. 
     78 
     79=== Using a comma delimited file - CSV === 
     80See [http://trac.edgewall.org/attachment/wiki/TracSynchronize/csv2trac.2.py] for details.  This approach is particularly useful if one needs to enter a large number of tickets by hand. (note that the ticket type type field, (task etc...) is also needed for this script to work with more recent Trac releases)