Changes between Initial Version and Version 1 of TracImport

11/05/16 17:06:47 (5 years ago)



  • TracImport

    v1 v1  
     1= Importing ticket data
     5To migrate issue tickets from other issue-tracking systems into Trac or perform housekeeping actions on tickets or simply synchronize different databases, there are some tools, plugins and scripts available.
     7== !TicketImportPlugin
     9[ TicketImportPlugin]: a plugin that lets you import or update into Trac a series of tickets from a '''CSV file''' or (if the [ xlrd library] is installed) from an '''Excel spreadsheet'''.
     11== !ExportImportXlsPlugin
     13[ ExportImportXlsPlugin]: a plugin that adds an admin panel for exporting and importing tickets via '''XLS file'''. Requires the python packages xlwt/rxld.
     15== Bugzilla
     17[ 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/] script, available in the contrib/ directory of the Trac distribution.
     21bugzilla2trac - Imports a bug database from Bugzilla into Trac.
     23Usage: [options]
     25Available 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
     34Additional configuration options can be defined directly in the script.
     37Currently, 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)
     43The 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.
     48For more details on the available options, see the configuration section at the top of the script.
     50=== Known Issues
     52Don't merge this section in the default page
     56The 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.
     58== Jira
     60[ JiraToTracIntegration]: a plugin that provides tools to import Atlassian Jira backup files into Trac. The plugin 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 [th:XmlRpcPlugin].
     63 - Generates a htpasswd file containing the imported Jira users and their SHA-512 base64 encoded passwords.
     65== Mantis
     67[ MantisImportScript]: a script to import the following type of data from Mantis into Trac:
     68 * bugs
     69 * bug comments
     70 * bug activity (field changes)
     71 * attachments (as long as the files live in the mantis database, not on the filesystem).
     73== !PlanetForge
     75[ 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. Has no 'import' feature.
     77== Scarab
     79[ ScarabToTracScript]: a script that migrates Scarab issues to Trac tickets. Requires [th:XmlRpcPlugin].
     81== Sourceforge
     83[ SfnToTracScript]: importer of !SourceForge's new backup file (originated from #Trac3521).
     84Also, ticket data can be imported from Sourceforge using the [trac:browser:trunk/contrib/] script, available in the contrib/ directory of the Trac distribution.
     86== Other
     88Since 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 [ sqlite] command line to look at the tables and import them from your application.
     90=== Comma delimited file - CSV
     92See [] 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.
     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