Home

Documentation

Project Support

Changes in Version 1 of TracImport

Author:
trac
Timestamp:
Wed Aug 23 17:34:43 2006

Legend:

Unmodified
Added
Removed
Modified

  • TracImport

    v0 v1
      1  = Importing ticket data = 
      2   
      3  == Bugzilla == 
      4   
      5  Ticket data can be imported from Bugzilla using the bugzilla2trac.py script, available in the contrib/ directory of the Trac distribution. 
      6   
      7  {{{ 
      8  $ bugzilla2trac.py 
      9  bugzilla2trac - Imports a bug database from Bugzilla into Trac. 
      10   
      11  Usage: bugzilla2trac.py [options] 
      12   
      13  Available 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   
      22  Additional configuration options can be defined directly in the script. 
      23  }}} 
      24   
      25  Currently, the following data is imported from Bugzilla: 
      26   
      27    * bugs 
      28    * bug activity (field changes) 
      29    * bug attachments 
      30   
      31  The 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   
      39  For more details on the available options, see the configuration section at the top of the script. 
      40   
      41  == Sourceforge == 
      42   
      43  Ticket data can be imported from Sourceforge using the sourceforge2trac.py script, available in the contrib/ directory of the Trac distribution.