| | 1 | = Importing ticket data |
| | 2 | |
| | 3 | [[PageOutline(2-5,Contents,pullout)]] |
| | 4 | |
| | 5 | To 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. |
| | 6 | |
| | 7 | == !TicketImportPlugin |
| | 8 | |
| | 9 | [https://trac-hacks.org/wiki/TicketImportPlugin TicketImportPlugin]: a plugin that lets you import or update into Trac a series of tickets from a '''CSV file''' or (if the [https://pypi.python.org/pypi/xlrd xlrd library] is installed) from an '''Excel spreadsheet'''. |
| | 10 | |
| | 11 | == !ExportImportXlsPlugin |
| | 12 | |
| | 13 | [https://trac-hacks.org/wiki/ExportImportXlsPlugin ExportImportXlsPlugin]: a plugin that adds an admin panel for exporting and importing tickets via '''XLS file'''. Requires the python packages xlwt/rxld. |
| | 14 | |
| | 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:branches/1.2-stable/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the `contrib/` directory of the Trac distribution. |
| | 18 | |
| | 19 | {{{#!python |
| | 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 an 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 | == Jira |
| | 51 | |
| | 52 | [https://trac-hacks.org/wiki/JiraToTracIntegration 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: |
| | 53 | - Parses the Jira backup XML file. |
| | 54 | - Sends the imported Jira data and attachments to Trac using the [https://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]. |
| | 55 | - Generates a htpasswd file containing the imported Jira users and their SHA-512 base64 encoded passwords. |
| | 56 | |
| | 57 | == Mantis |
| | 58 | |
| | 59 | [https://trac-hacks.org/wiki/MantisImportScript MantisImportScript]: a script to import the following type of data from Mantis into Trac: |
| | 60 | * bugs |
| | 61 | * bug comments |
| | 62 | * bug activity (field changes) |
| | 63 | * attachments (as long as the files live in the mantis database, not on the filesystem). |
| | 64 | |
| | 65 | == !PlanetForge |
| | 66 | |
| | 67 | [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. |
| | 68 | |
| | 69 | == Scarab |
| | 70 | |
| | 71 | [https://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript]: a script that migrates Scarab issues to Trac tickets. Requires [https://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]. |
| | 72 | |
| | 73 | == Sourceforge |
| | 74 | |
| | 75 | [https://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript]: importer of !SourceForge's new backup file (originated from #Trac3521). |
| | 76 | Also, ticket data can be imported from Sourceforge using the [trac:browser:trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution. |
| | 77 | |
| | 78 | == Other |
| | 79 | |
| | 80 | 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. |
| | 81 | |
| | 82 | === Comma delimited file - CSV |
| | 83 | |
| | 84 | 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. |
| | 85 | |
| | 86 | 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. |
| | 87 | |
| | 88 | ---- |
| | 89 | See also: |
| | 90 | * to import/export wiki pages: TracAdmin, |
| | 91 | * to export tickets: TracTickets, TracQuery |
