Changes between Version 4 and Version 5 of TracImport
- Timestamp:
- Sep 18, 2019 12:25:56 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracImport
v4 v5 1 = Importing ticket data = 2 [[PageOutline]] 1 = Importing ticket data 3 2 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. 3 [[PageOutline(2-5,Contents,pullout)]] 5 4 6 == !TicketImportPlugin == 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. 7 6 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'''. 7 == !TicketImportPlugin 9 8 10 == !ExportImportXlsPlugin == 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'''. 11 10 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. 11 == !ExportImportXlsPlugin 13 12 14 == Bugzilla == 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. 15 14 16 [http://trac-hacks.org/wiki/BugzillaIssueTrackingPlugin BugzillaIssueTrackingPlugin]: 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. 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:trunk/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the contrib/ directory of the Trac distribution. 17 18 18 19 {{{ … … 35 36 36 37 Currently, the following data is imported from Bugzilla: 37 38 39 40 38 * bugs 39 * bug activity (field changes) 40 * bug attachments 41 * user names and passwords (put into a htpasswd file) 41 42 42 43 The script provides a number of features to ease the conversion, such as: 43 44 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 * 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. 46 47 47 48 For more details on the available options, see the configuration section at the top of the script. 48 49 49 === Known Issues === 50 {{{ 51 #!comment 52 Don't merge this section in the default page 50 === Known Issues 51 {{{#!comment 52 Don't merge this section in the default page 53 53 }}} 54 54 [[TicketQuery(keywords=~bugzilla,status=!closed)]] … … 56 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 57 58 == Jira ==58 == Jira 59 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 62 - Sends the imported Jira data and attachments to Trac using the [http://trac-hacks.org/wiki/XmlRpcPluginXmlRpcPlugin].63 60 [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: 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. 64 64 65 == Mantis ==65 == Mantis 66 66 67 [http ://trac-hacks.org/wiki/MantisImportScript MantisImportScript]: script to import the followingdata from Mantis into Trac:68 69 70 71 * attachments (as long as the files live in the mantis db, not on the filesystem).67 [https://trac-hacks.org/wiki/MantisImportScript 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). 72 72 73 == !PlanetForge ==73 == !PlanetForge 74 74 75 [http ://trac-hacks.org/wiki/PlanetForgeImportExportPlugin PlanetForgeImportExportPlugin]: this plugin exports Trac data (wiki, tickets, compoments, permissions, repositories, etc.) using the open format designed by the COCLICOproject. It extends the webadmin panel and the 'trac admin ...' command. Has no 'import' feature.75 [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. 76 76 77 == Scarab ==77 == Scarab 78 78 79 [http ://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript]: script that migrates Scarab issues to Trac tickets. Requires [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]79 [https://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript]: a script that migrates Scarab issues to Trac tickets. Requires [th:XmlRpcPlugin]. 80 80 81 == Sourceforge ==81 == Sourceforge 82 82 83 [http ://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript]: importer of !SourceForge's new backup file (originated from #Trac3521).83 [https://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript]: importer of !SourceForge's new backup file (originated from #Trac3521). 84 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. 85 85 86 == Other ==86 == Other 87 87 88 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 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. 90 === Comma delimited file - CSV 91 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 type field, (task etc.) is also needed for this script to work with more recent Trac releases. 93 92 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. 93 95