Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Changes from Version 1 of TracImport

Author:
trac (IP: 0.0.0.0)
Timestamp:
09/19/05 15:24:32 (14 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracImport

    v v1  
     1= Importing ticket data = 
     2 
     3== Bugzilla == 
     4 
     5Ticket data can be imported from Bugzilla using the [source: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 [source:http://projects.edgewall.com/trac/file/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.   
     48Currently, the following data is imported from Mantis: 
     49  * bugs 
     50  * bug comments 
     51  * bug activity (field changes) 
     52 
     53Attachments 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. 
     54 
     55mantis2trac.py has the same parameters as the bugzilla2trac.py script: 
     56{{{ 
     57mantis2trac - Imports a bug database from Mantis into Trac. 
     58 
     59Usage: mantis2trac.py [options] 
     60 
     61Available Options: 
     62  --db <MySQL dbname>              - Mantis database 
     63  --tracenv /path/to/trac/env      - Full path to Trac db environment 
     64  -h | --host <MySQL hostname>     - Mantis DNS host name 
     65  -u | --user <MySQL username>     - Effective Mantis database user 
     66  -p | --passwd <MySQL password>   - Mantis database user password 
     67  -c | --clean                     - Remove current Trac tickets before importing 
     68  --help | help                    - This help info 
     69 
     70Additional configuration options can be defined directly in the script. 
     71}}}