Changes between Initial Version and Version 1 of TracImport

03/04/15 13:21:40 (7 years ago)



  • TracImport

    v1 v1  
     1= Importing ticket data =
     4By means of migrating from other issue-tracking systems, perform some external actions over tickets or simply synchronize different data bases, there are some available tools, plug-ins or scripts which lets you import or up-date tickets into Trac.
     6Below, follows a collection of some of those.
     8== !TicketImportPlugin ==
     10 th:TicketImportPlugin:: mainly, but not only, this plug-in lets you import or up-date into Trac a series of tickets from a '''CSV file''' or (if the [ xlrd library] is installed) from an '''Excel file'''.
     12== !ExportImportXlsPlugin ==
     14 th:ExportImportXlsPlugin:: this plug-in add an admin panel for export and import tickets via '''XLS file'''.
     15  * It depends on the python packages xlwt/rxld.
     17== Bugzilla ==
     19 th:BugzillaIssueTrackingPlugin:: integrates Bugzilla into Trac keeping TracLinks
     21Ticket data can be imported from Bugzilla using the [] script, available in the contrib/ directory of the Trac distribution.
     25bugzilla2trac - Imports a bug database from Bugzilla into Trac.
     27Usage: [options]
     29Available Options:
     30  --db <MySQL dbname>              - Bugzilla's database
     31  --tracenv /path/to/trac/env      - full path to Trac db environment
     32  -h | --host <MySQL hostname>     - Bugzilla's DNS host name
     33  -u | --user <MySQL username>     - effective Bugzilla's database user
     34  -p | --passwd <MySQL password>   - Bugzilla's user password
     35  -c | --clean                     - remove current Trac tickets before importing
     36  --help | help                    - this help info
     38Additional configuration options can be defined directly in the script.
     41Currently, the following data is imported from Bugzilla:
     43  * bugs
     44  * bug activity (field changes)
     45  * bug attachments
     46  * user names and passwords (put into a htpasswd file)
     48The script provides a number of features to ease the conversion, such as:
     50  * PRODUCT_KEYWORDS:  Trac doesn't have the concept of products, so the script provides the ability to attach a ticket keyword instead.
     52  * IGNORE_COMMENTS:  Don't import Bugzilla comments that match a certain regexp.
     54  * 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.
     56For more details on the available options, see the configuration section at the top of the script.
     58== Jira ==
     60 th:JiraToTracIntegration:: provides tools to import Atlassian Jira backup files into Trac. The plug-in consists of a Python 3.1 commandline tool that:
     61   - Parses the Jira backup XML file
     62   - Sends the imported Jira data and attachments to Trac using the [ XmlRpcPlugin]
     63   - Generates a htpasswd file containing the imported Jira users and their SHA-512 base64 encoded passwords
     65== Mantis ==
     67 th:MantisImportScript:: script to import from Mantis into Trac the following data:
     68  * bugs
     69  * bug comments
     70  * bug activity (field changes)
     71  * attachments (as long as the files live in the mantis db, not on the filesystem) .
     73== !PlanetForge ==
     75 th:PlanetForgeImportExportPlugin:: this plugin exports Trac data (wiki, tickets, compoments, permissions, repositories, etc.) using the open format designed by the COCLICO project. It extends the webadmin panel and the 'trac admin ...' command. Still has no 'import' feature.
     77== Scarab ==
     79 th:ScarabToTracScript:: script that migrates Scarab issues to Trac tickets
     80    * Requires [ XmlRpcPlugin]
     82== Sourceforge ==
     84 th:SfnToTracScript:: importer of !SourceForge's new backup file (originated from #Trac3521)
     86Also, ticket data can be imported from Sourceforge using the [] script, available in the contrib/ directory of the Trac distribution.
     88== Other ==
     90Since trac uses a SQL database to store the data, you can import from other systems by examining the database tables. Just go into [ sqlite] command line to look at the tables and import into them from your application.
     92=== Comma delimited file - CSV ===
     93See [] 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)
     94Comments 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.
     97See also:
     98 * to import/export wiki pages: TracAdmin,
     99 * to export tickets: TracTickets, TracQuery