Changes between Initial Version and Version 1 of TracImport

Show
Ignore:
Timestamp:
31-05-11 17:45:08 (3 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracImport

    v1 v1  
     1= Importing ticket data = 
     2 
     3== Bugzilla == 
     4 
     5Ticket data can be imported from Bugzilla using the [http://trac.edgewall.org/browser/trunk/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the contrib/ directory of the Trac distribution. 
     6 
     7{{{ 
     8$ bugzilla2trac.py 
     9bugzilla2trac - Imports a bug database from Bugzilla into Trac. 
     10 
     11Usage: bugzilla2trac.py [options] 
     12 
     13Available Options: 
     14  --db <MySQL dbname>              - Bugzilla's database 
     15  --tracenv /path/to/trac/env      - full path to Trac db environment 
     16  -h | --host <MySQL hostname>     - Bugzilla's DNS host name 
     17  -u | --user <MySQL username>     - effective Bugzilla's database user 
     18  -p | --passwd <MySQL password>   - Bugzilla's user password 
     19  -c | --clean                     - remove current Trac tickets before importing 
     20  --help | help                    - this help info 
     21 
     22Additional configuration options can be defined directly in the script. 
     23}}} 
     24 
     25Currently, the following data is imported from Bugzilla: 
     26 
     27  * bugs 
     28  * bug activity (field changes) 
     29  * bug attachments 
     30  * user names and passwords (put into a htpasswd file) 
     31 
     32The script provides a number of features to ease the conversion, such as: 
     33 
     34  * PRODUCT_KEYWORDS:  Trac doesn't have the concept of products, so the script provides the ability to attach a ticket keyword instead. 
     35 
     36  * IGNORE_COMMENTS:  Don't import Bugzilla comments that match a certain regexp. 
     37 
     38  * STATUS_KEYWORDS:  Attach ticket keywords for the Bugzilla statuses not available in Trac.  By default, the 'VERIFIED' and 'RELEASED' Bugzilla statuses are translated into Trac keywords. 
     39 
     40For more details on the available options, see the configuration section at the top of the script. 
     41 
     42== Sourceforge == 
     43 
     44Ticket data can be imported from Sourceforge using the [http://trac.edgewall.org/browser/trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution. 
     45 
     46== Mantis == 
     47 
     48NB! The mantis2trac script now lives at http://trac-hacks.org/wiki/MantisImportScript . You can always get the latest version from http://trac-hacks.org/changeset/latest/mantisimportscript?old_path=/&filename=mantisimportscript&format=zip 
     49 
     50Mantis bugs can be imported using the attached script. 
     51 
     52Currently, the following data is imported from Mantis: 
     53  * bugs 
     54  * bug comments 
     55  * bug activity (field changes) 
     56  * attachments (as long as the files live in the mantis db, not on the filesystem)  
     57 
     58If 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. 
     59 
     60mantis2trac.py has the same parameters as the bugzilla2trac.py script: 
     61{{{ 
     62mantis2trac - Imports a bug database from Mantis into Trac. 
     63 
     64Usage: mantis2trac.py [options]  
     65 
     66Available Options: 
     67  --db <MySQL dbname>              - Mantis database 
     68  --tracenv /path/to/trac/env      - Full path to Trac db environment 
     69  -h | --host <MySQL hostname>     - Mantis DNS host name 
     70  -u | --user <MySQL username>     - Effective Mantis database user 
     71  -p | --passwd <MySQL password>   - Mantis database user password 
     72  -c | --clean                     - Remove current Trac tickets before importing 
     73  --help | help                    - This help info 
     74 
     75Additional configuration options can be defined directly in the script. 
     76}}}  
     77 
     78== Other == 
     79 
     80Since 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. 
     81 
     82=== Using a comma delimited file - CSV === 
     83See [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) 
     84