Changes between Version 2 and Version 3 of TracImport
- Timestamp:
- Jun 9, 2024, 11:14:44 AM (4 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracImport
v2 v3 3 3 [[PageOutline(2-5,Contents,pullout)]] 4 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. 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 6 7 7 == !TicketImportPlugin 8 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'''.9 [https://trac-hacks.org/wiki/TicketImportPlugin TicketImportPlugin]: a plugin that allows you to import or update 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''' into Trac. 10 10 11 11 == !ExportImportXlsPlugin 12 12 13 [https://trac-hacks.org/wiki/ExportImportXlsPlugin ExportImportXlsPlugin]: a plugin that a dds an admin panel for exporting and importing tickets via '''XLS file'''. Requires the python packages xlwt/rxld.13 [https://trac-hacks.org/wiki/ExportImportXlsPlugin ExportImportXlsPlugin]: a plugin that allows you to export and import tickets from a '''XLS file'''. Requires the Python packages xlwt/rxld. 14 14 15 15 == Bugzilla 16 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: trunk/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the contrib/directory of the Trac distribution.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.4-stable/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the `contrib/` directory of the Trac distribution. 18 18 19 {{{ 19 {{{#!python 20 20 $ bugzilla2trac.py 21 21 bugzilla2trac - Imports a bug database from Bugzilla into Trac. … … 39 39 * bug activity (field changes) 40 40 * bug attachments 41 * user names and passwords (put into a htpasswd file)41 * user names and passwords (put into an htpasswd file) 42 42 43 43 The script provides a number of features to ease the conversion, such as: … … 48 48 For more details on the available options, see the configuration section at the top of the script. 49 49 50 === Known Issues51 {{{#!comment52 Don't merge this section in the default page53 }}}54 [[TicketQuery(keywords=~bugzilla,status=!closed)]]55 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 50 == Jira 59 51 60 [https://trac-hacks.org/wiki/JiraToTracIntegration JiraToTracIntegration]: a plugin that provides toolsto import Atlassian Jira backup files into Trac. The plugin consists of a Python 3.1 commandline tool that:52 [https://trac-hacks.org/wiki/JiraToTracIntegration JiraToTracIntegration]: a plugin that allows you to import Atlassian Jira backup files into Trac. The plugin consists of a Python 3.1 commandline tool that: 61 53 - Parses the Jira backup XML file. 62 - Sends the imported Jira data and attachments to Trac using the [ th:XmlRpcPlugin].54 - Sends the imported Jira data and attachments to Trac using the [https://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]. 63 55 - Generates a htpasswd file containing the imported Jira users and their SHA-512 base64 encoded passwords. 64 56 … … 73 65 == !PlanetForge 74 66 75 [https://trac-hacks.org/wiki/PlanetForgeImportExportPlugin PlanetForgeImportExportPlugin]: this plugin exports Trac data (wiki, tickets, compo ments, 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.67 [https://trac-hacks.org/wiki/PlanetForgeImportExportPlugin PlanetForgeImportExportPlugin]: this plugin exports Trac data (wiki, tickets, components, 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. 76 68 77 69 == Scarab 78 70 79 [https://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript]: a script that migrates Scarab issues to Trac tickets. Requires [ th:XmlRpcPlugin].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]. 80 72 81 73 == Sourceforge 82 74 83 75 [https://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.76 Also, ticket data can be imported from Sourceforge using the [trac:browser:branches/1.4-stable/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution. 85 77 86 78 == Other 87 79 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 tablesand import them from your application.80 Since Trac uses a SQL database to store the data, you can also import ticket data from other systems by creating a mapping between the relevant database tables. Just go into [https://www.sqlite.org/sqlite.html sqlite] command line to look at the tables, create the column-to-column mapping as an SQL script and import them from your application. 89 81 90 82 === Comma delimited file - CSV 91 83 92 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 typefield, (task etc.) is also needed for this script to work with more recent Trac releases.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 field, (task etc.) is also needed for this script to work with more recent Trac releases. 93 85 94 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. 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. 95 87 96 88 ---- 97 See also: 98 * to import/export wiki pages: TracAdmin, 89 See also: 90 * to import/export wiki pages: TracAdmin, 99 91 * to export tickets: TracTickets, TracQuery