| | 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. |
| 68 | | Available 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 |
| | 79 | [http://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript]: script that migrates Scarab issues to Trac tickets. Requires [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] |
| 80 | | == Jira == |
| 81 | | |
| 82 | | The [http://trac-hacks.org/wiki/JiraToTracIntegration Jira2Trac plugin] provides you with tools to import Atlassian Jira backup files into Trac. |
| 83 | | |
| 84 | | The plugin consists of a Python 3.1 commandline tool that: |
| 85 | | |
| 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 |
| | 83 | [http://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript]: importer of !SourceForge's new backup file (originated from #Trac3521). |
| | 84 | 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. |
| 94 | | === Using a comma delimited file - CSV === |
| 95 | | See [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) |
| 96 | | 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. |
| | 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. |
| 98 | | === Using an Excel (.xls) or comma delimited file (.csv) === |
| 99 | | This 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. |
| 100 | | |
| 101 | | You can also use it to modify tickets in batch, by saving a report as CSV, editing the CSV file, and re-importing the tickets. |
| 102 | | |
| 103 | | This 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. |
| 104 | | |
| 105 | | Based on the ticket id (or, if no id exists, on the summary) in the imported file, tickets are either created or updated. |
| 106 | | |
| 107 | | |
| | 94 | ---- |
| | 95 | See also: |
| | 96 | * to import/export wiki pages: TracAdmin, |
| | 97 | * to export tickets: TracTickets, TracQuery |
