Changes between Version 1 and Version 2 of TracImport
- Timestamp:
- Mar 2, 2014, 3:22:52 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracImport
v1 v2 1 1 = Importing ticket data = 2 [[PageOutline]] 3 4 By means of migrating from other issue-tracking systems, perform some external actions over tickets or simply synchronize different data bases, there are some available tools, plug-ins or scripts which lets you import or up-date tickets into Trac. 5 6 Below, follows a collection of some of those. 7 8 == !TicketImportPlugin == 9 10 [http://trac-hacks.org/wiki/TicketImportPlugin TicketImportPlugin] :: mainly, but not only, this plug-in lets you import or up-date 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 file'''. 11 12 == !ExportImportXlsPlugin == 13 14 [http://trac-hacks.org/wiki/ExportImportXlsPlugin ExportImportXlsPlugin] :: this plug-in add an admin panel for export and import tickets via '''XLS file'''. 15 * It depends on the python packages xlwt/rxld. 2 16 3 17 == Bugzilla == 18 19 [http://trac-hacks.org/wiki/BugzillaIssueTrackingPlugin BugzillaIssueTrackingPlugin] :: integrates Bugzilla into Trac keeping TracLinks 4 20 5 21 Ticket data can be imported from Bugzilla using the [http://trac.edgewall.org/browser/trunk/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the contrib/ directory of the Trac distribution. … … 40 56 For more details on the available options, see the configuration section at the top of the script. 41 57 42 == Sourceforge==58 == Jira == 43 59 44 Ticket data can be imported from Sourceforge using the [http://trac.edgewall.org/browser/trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution. 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 45 64 46 65 == Mantis == 47 66 48 NB! The mantis2trac script now lives at http://trac-hacks.org/wiki/MantisImportScript . You can always get the latest version from http://trac-hacks.org/changeset/latest/mantisimportscript?old_path=/&filename=mantisimportscript&format=zip 49 50 Mantis bugs can be imported using the attached script. 51 52 Currently, the following data is imported from Mantis: 67 [http://trac-hacks.org/wiki/MantisImportScript MantisImportScript] :: script to import from Mantis into Trac the following data: 53 68 * bugs 54 69 * bug comments 55 70 * bug activity (field changes) 56 * attachments (as long as the files live in the mantis db, not on the filesystem) 71 * attachments (as long as the files live in the mantis db, not on the filesystem) . 57 72 58 If you use the script, please read the NOTES section (at the top of the file) and make sure you adjust the config parameters for your environment. 73 == !PlanetForge == 59 74 60 mantis2trac.py has the same parameters as the bugzilla2trac.py script: 61 {{{ 62 mantis2trac - Imports a bug database from Mantis into Trac. 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 COCLICO project. It extends the webadmin panel and the 'trac admin ...' command. Still has no 'import' feature. 63 76 64 Usage: mantis2trac.py [options] 77 == Scarab == 65 78 66 Available Options: 67 --db <MySQL dbname> - Mantis database 68 --tracenv /path/to/trac/env - Full path to Trac db environment 69 -h | --host <MySQL hostname> - Mantis DNS host name 70 -u | --user <MySQL username> - Effective Mantis database user 71 -p | --passwd <MySQL password> - Mantis database user password 72 -c | --clean - Remove current Trac tickets before importing 73 --help | help - This help info 79 [http://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript] :: script that migrates Scarab issues to Trac tickets 80 * Requires [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] 74 81 75 Additional configuration options can be defined directly in the script. 76 }}} 82 == Sourceforge == 83 84 [http://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript] :: importer of !SourceForge's new backup file (originated from #Trac3521) 85 86 Also, ticket data can be imported from Sourceforge using the [http://trac.edgewall.org/browser/trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution. 77 87 78 88 == Other == … … 80 90 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. 81 91 82 === Using a comma delimited file - CSV === 83 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) 92 === Comma delimited file - CSV === 93 See [http://trac.edgewall.org/attachment/wiki/TracSynchronize/csv2trac.2.py 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) 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. 84 95 96 ---- 97 See also: 98 * to import/export wiki pages: TracAdmin, 99 * to export tickets: TracTickets, TracQuery