Changes between Initial Version and Version 1 of TracImport


Ignore:
Timestamp:
Jan 16, 2006, 11:00:35 PM (16 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://projects.edgewall.com/trac/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
     31The script provides a number of features to ease the conversion, such as:
     32
     33  * PRODUCT_KEYWORDS:  Trac doesn't have the concept of products, so the script provides the ability to attach a ticket keyword instead.
     34
     35  * IGNORE_COMMENTS:  Don't import Bugzilla comments that match a certain regexp.
     36
     37  * 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.
     38
     39For more details on the available options, see the configuration section at the top of the script.
     40
     41== Sourceforge ==
     42
     43Ticket 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.
     44
     45== Mantis ==
     46
     47Mantis bugs can be imported using the attached script.
     48
     49Currently, the following data is imported from Mantis:
     50  * bugs
     51  * bug comments
     52  * bug activity (field changes)
     53
     54Attachments 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.
     55
     56mantis2trac.py has the same parameters as the bugzilla2trac.py script:
     57{{{
     58mantis2trac - Imports a bug database from Mantis into Trac.
     59
     60Usage: mantis2trac.py [options]
     61
     62Available Options:
     63  --db <MySQL dbname>              - Mantis database
     64  --tracenv /path/to/trac/env      - Full path to Trac db environment
     65  -h | --host <MySQL hostname>     - Mantis DNS host name
     66  -u | --user <MySQL username>     - Effective Mantis database user
     67  -p | --passwd <MySQL password>   - Mantis database user password
     68  -c | --clean                     - Remove current Trac tickets before importing
     69  --help | help                    - This help info
     70
     71Additional configuration options can be defined directly in the script.
     72}}}
     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.