Changes between Version 1 and Version 2 of TracImport


Ignore:
Timestamp:
Jul 30, 2012 5:30:50 PM (12 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracImport

    v1 v2  
    11= Importing ticket data = 
     2[[PageOutline]] 
     3 
     4By 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 
     6Below, follows a collection of some of those. 
     7 
     8== !TicketImportPlugin == 
     9 
     10 th: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 th: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. 
    216 
    317== Bugzilla == 
    418 
    5 Ticket data can be imported from Bugzilla using the [http://projects.edgewall.com/trac/browser/trunk/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the contrib/ directory of the Trac distribution. 
     19 th:BugzillaIssueTrackingPlugin:: integrates Bugzilla into Trac keeping TracLinks 
     20 
     21Ticket 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. 
    622 
    723{{{ 
    … …  
    4056For more details on the available options, see the configuration section at the top of the script. 
    4157 
    42 == Sourceforge == 
     58== Jira == 
    4359 
    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. 
     60 th: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 
    4564 
    4665== Mantis == 
    4766 
    48 Mantis bugs can be imported using the attached script. 
    49  
    50 Currently, the following data is imported from Mantis: 
     67 th:MantisImportScript:: script to import from Mantis into Trac the following data: 
    5168  * bugs 
    5269  * bug comments 
    5370  * bug activity (field changes) 
     71  * attachments (as long as the files live in the mantis db, not on the filesystem) . 
    5472 
    55 Attachments are NOT imported.  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 == 
    5674 
    57 mantis2trac.py has the same parameters as the bugzilla2trac.py script: 
    58 {{{ 
    59 mantis2trac - Imports a bug database from Mantis into Trac. 
     75 th: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.  
    6076 
    61 Usage: mantis2trac.py [options]  
     77== Scarab == 
    6278 
    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 th:ScarabToTracScript:: script that migrates Scarab issues to Trac tickets 
     80    * Requires [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] 
    7181 
    72 Additional configuration options can be defined directly in the script. 
    73 }}}  
     82== Sourceforge == 
     83 
     84 th:SfnToTracScript:: importer of !SourceForge's new backup file (originated from #Trac3521) 
     85 
     86Also, 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. 
    7487 
    7588== Other == 
    … …  
    7790Since 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. 
    7891 
    79 === Using a comma delimited file - CSV === 
     92=== Comma delimited file - CSV === 
    8093See [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) 
     94Comments 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 
     96---- 
     97See also:  
     98 * to import/export wiki pages: TracAdmin,  
     99 * to export tickets: TracTickets, TracQuery