| 15 |   | == Bugzilla | 
          
          
            | 16 |   |  | 
          
          
            | 17 |   | [https://trac-hacks.org/wiki/BugzillaIssueTrackingPlugin BugzillaIssueTrackingPlugin]: a plugin that integrates Bugzilla issue data into Trac keeping TracLinks. Ticket data can be imported from Bugzilla using the [trac:browser:trunk/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the contrib/ directory of the Trac distribution. | 
          
          
            | 18 |   |  | 
          
          
            | 19 |   | {{{ | 
          
          
            | 20 |   | $ bugzilla2trac.py | 
          
          
            | 21 |   | bugzilla2trac - Imports a bug database from Bugzilla into Trac. | 
          
          
            | 22 |   |  | 
          
          
            | 23 |   | Usage: bugzilla2trac.py [options] | 
          
          
            | 24 |   |  | 
          
          
            | 25 |   | Available Options: | 
          
          
            | 26 |   |   --db <MySQL dbname>              - Bugzilla's database | 
          
          
            | 27 |   |   --tracenv /path/to/trac/env      - full path to Trac db environment | 
          
          
            | 28 |   |   -h | --host <MySQL hostname>     - Bugzilla's DNS host name | 
          
          
            | 29 |   |   -u | --user <MySQL username>     - effective Bugzilla's database user | 
          
          
            | 30 |   |   -p | --passwd <MySQL password>   - Bugzilla's user password | 
          
          
            | 31 |   |   -c | --clean                     - remove current Trac tickets before importing | 
          
          
            | 32 |   |   --help | help                    - this help info | 
          
          
            | 33 |   |  | 
          
          
            | 34 |   | Additional configuration options can be defined directly in the script. | 
          
          
            | 35 |   | }}} | 
          
          
            | 36 |   |  | 
          
          
            | 37 |   | Currently, the following data is imported from Bugzilla: | 
          
          
            | 38 |   |  * bugs | 
          
          
            | 39 |   |  * bug activity (field changes) | 
          
          
            | 40 |   |  * bug attachments | 
          
          
            | 41 |   |  * user names and passwords (put into a htpasswd file) | 
          
          
            | 42 |   |  | 
          
          
            | 43 |   | The script provides a number of features to ease the conversion, such as: | 
          
          
            | 44 |   |  * PRODUCT_KEYWORDS: Trac has no concept of products, so the script provides the ability to attach a ticket keyword instead. | 
          
          
            | 45 |   |  * IGNORE_COMMENTS: Don't import Bugzilla comments that match a certain regexp. | 
          
          
            | 46 |   |  * 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. | 
          
          
            | 47 |   |  | 
          
          
            | 48 |   | For more details on the available options, see the configuration section at the top of the script. | 
          
          
            | 49 |   |  | 
          
          
            | 50 |   | === Known Issues | 
          
          
            | 51 |   | {{{#!comment | 
          
          
            | 52 |   | Don't merge this section in the default page | 
          
          
            | 53 |   | }}} | 
          
          
            | 54 |   | [[TicketQuery(keywords=~bugzilla,status=!closed)]] | 
          
          
            | 55 |   |  | 
          
          
            | 56 |   | The adequate milestone for valid bugzilla2trac issue is usually ''Not applicable'', which means that fixes to the contributed script are not planned for a particular Trac release, but can happen anytime. | 
          
          
            | 57 |   |  | 
          
        
        
          
            | 75 |   | [https://trac-hacks.org/wiki/PlanetForgeImportExportPlugin PlanetForgeImportExportPlugin]: this plugin exports Trac data (wiki, tickets, compoments, permissions, repositories, etc.) using the open format designed by the [https://gforge.inria.fr/projects/coclico/ COCLICO] project. It extends the webadmin panel and the 'trac admin ...' command. Has no 'import' feature.  | 
          
          
            |   | 32 | [https://trac-hacks.org/wiki/PlanetForgeImportExportPlugin PlanetForgeImportExportPlugin]: this plugin exports Trac data (wiki, tickets, compoments, permissions, repositories, etc.) using the open format designed by the [https://gforge.inria.fr/projects/coclico/ COCLICO] project. It extends the webadmin panel and the 'trac admin ...' command. Has no 'import' feature. | 
          
        
        
          
            | 88 |   | Since Trac uses a SQL database to store the data, you can also custom-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 them from your application. | 
          
          
            | 89 |   |  | 
          
          
            | 90 |   | === Comma delimited file - CSV | 
          
          
            | 91 |   |  | 
          
          
            | 92 |   | See [trac:attachment:csv2trac.2.py:wiki:TracSynchronize csv2trac.2.py] for details. This approach is particularly useful if you need 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. | 
          
          
            | 93 |   |  | 
          
          
            | 94 |   | Comments on script: The script has an error on line 168: 'Ticket' needs to be 'ticket'. Also, the listed values for severity and priority are swapped.  | 
          
          
            |   | 40 | Since Trac uses a SQL database to store the data, you can also custom-import from other systems by examining the database tables. Just go into [https://www.sqlite.org/sqlite.html sqlite] command line to look at the tables and import them from your application. |