| | 2 | [[PageOutline]] |
| | 3 | |
| | 4 | To migrate issue tickets from other issue-tracking systems or perform housekeeping actions on tickets or simply synchronize different databases, there are some tools, plug-ins and scripts available, which let you import or update tickets into Trac. |
| | 5 | |
| | 6 | == !TicketImportPlugin == |
| | 7 | |
| | 8 | [http://trac-hacks.org/wiki/TicketImportPlugin TicketImportPlugin]: this plug-in lets you import or update into Trac a series of tickets from a '''CSV file''' or (if the [http://pypi.python.org/pypi/xlrd xlrd library] is installed) from an '''Excel spreadsheet'''. |
| | 9 | |
| | 10 | == !ExportImportXlsPlugin == |
| | 11 | |
| | 12 | [http://trac-hacks.org/wiki/ExportImportXlsPlugin ExportImportXlsPlugin]: this plug-in adds an admin panel for exporting and importing tickets via '''XLS file'''. Requires the python packages xlwt/rxld. |
| 33 | | |
| 34 | | * PRODUCT_KEYWORDS: Trac doesn't have the concept of products, so the script provides the ability to attach a ticket keyword instead. |
| 35 | | |
| 36 | | * IGNORE_COMMENTS: Don't import Bugzilla comments that match a certain regexp. |
| 37 | | |
| 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. |
| | 43 | * PRODUCT_KEYWORDS: Trac has no concept of products, so the script provides the ability to attach a ticket keyword instead. |
| | 44 | * IGNORE_COMMENTS: Don't import Bugzilla comments that match a certain regexp. |
| | 45 | * 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. |
| 44 | | Ticket data can be imported from Sourceforge using the [http://projects.edgewall.com/trac/browser/trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution. |
| | 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 | |
| | 58 | == Jira == |
| | 59 | |
| | 60 | [http://trac-hacks.org/wiki/JiraToTracIntegration 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 [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]. |
| | 63 | - Generates a htpasswd file containing the imported Jira users and their SHA-512 base64 encoded passwords. |
| 63 | | Available Options: |
| 64 | | --db <MySQL dbname> - Mantis database |
| 65 | | --tracenv /path/to/trac/env - Full path to Trac db environment |
| 66 | | -h | --host <MySQL hostname> - Mantis DNS host name |
| 67 | | -u | --user <MySQL username> - Effective Mantis database user |
| 68 | | -p | --passwd <MySQL password> - Mantis database user password |
| 69 | | -c | --clean - Remove current Trac tickets before importing |
| 70 | | --help | help - This help info |
| | 79 | [http://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript]: script that migrates Scarab issues to Trac tickets. Requires [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] |
| 77 | | Since 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. |
| | 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 | 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. |
| | 92 | 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. |
| | 93 | |
| | 94 | ---- |
| | 95 | See also: |
| | 96 | * to import/export wiki pages: TracAdmin, |
| | 97 | * to export tickets: TracTickets, TracQuery |
