xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.

Changes between Initial Version and Version 1 of TracImport

05/31/11 12:07:54 (10 years ago)



  • TracImport

    v1 v1  
     1= Importing ticket data =
     3== Bugzilla ==
     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.
     8$ bugzilla2trac.py
     9bugzilla2trac - Imports a bug database from Bugzilla into Trac.
     11Usage: bugzilla2trac.py [options]
     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
     22Additional configuration options can be defined directly in the script.
     25Currently, the following data is imported from Bugzilla:
     27  * bugs
     28  * bug activity (field changes)
     29  * bug attachments
     30  * user names and passwords (put into a htpasswd file)
     32The script provides a number of features to ease the conversion, such as:
     34  * PRODUCT_KEYWORDS:  Trac doesn't have the concept of products, so the script provides the ability to attach a ticket keyword instead.
     36  * IGNORE_COMMENTS:  Don't import Bugzilla comments that match a certain regexp.
     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.
     40For more details on the available options, see the configuration section at the top of the script.
     42== Sourceforge ==
     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.
     46See #Trac3521 for an updated sourceforge2trac script.
     48== Mantis ==
     50The 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
     52Mantis bugs can be imported using the attached script.
     54Currently, the following data is imported from Mantis:
     55  * bugs
     56  * bug comments
     57  * bug activity (field changes)
     58  * attachments (as long as the files live in the mantis db, not on the filesystem)
     60If 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.
     62mantis2trac.py has the same parameters as the bugzilla2trac.py script:
     64mantis2trac - Imports a bug database from Mantis into Trac.
     66Usage: mantis2trac.py [options]
     68Available Options:
     69  --db <MySQL dbname>              - Mantis database
     70  --tracenv /path/to/trac/env      - Full path to Trac db environment
     71  -h | --host <MySQL hostname>     - Mantis DNS host name
     72  -u | --user <MySQL username>     - Effective Mantis database user
     73  -p | --passwd <MySQL password>   - Mantis database user password
     74  -c | --clean                     - Remove current Trac tickets before importing
     75  --help | help                    - This help info
     77Additional configuration options can be defined directly in the script.
     80== Jira ==
     82The [http://trac-hacks.org/wiki/JiraToTracIntegration Jira2Trac plugin] provides you with tools to import Atlassian Jira backup files into Trac.
     84The plugin consists of a Python 3.1 commandline tool that:
     86 - Parses the Jira backup XML file
     87 - Sends the imported Jira data and attachments to Trac using the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]
     88 - Generates a htpasswd file containing the imported Jira users and their SHA-512 base64 encoded passwords
     90== Other ==
     92Since 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.
     94=== Using a comma delimited file - CSV ===
     95See [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)
     96Comments 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.
     98=== Using an Excel (.xls) or comma delimited file (.csv) ===
     99This plugin http://trac-hacks.org/wiki/TicketImportPlugin lets you import into Trac a series of tickets from a CSV file or (if the xlrd library is installed) from an Excel file.
     101You can also use it to modify tickets in batch, by saving a report as CSV, editing the CSV file, and re-importing the tickets.
     103This plugin is very useful when starting a new project: you can import a list of requirements that may have come from meeting notes, list of features, other ticketing systems... It's also great to review the tickets off-line, or to do massive changes to tickets.
     105Based on the ticket id (or, if no id exists, on the summary) in the imported file, tickets are either created or updated.