Changes between Version 2 and Version 3 of TracImport


Ignore:
Timestamp:
08/29/13 12:47:07 (11 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracImport

    v2 v3  
    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 [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. 
    216 
    317== Bugzilla == 
     18 
     19 [http://trac-hacks.org/wiki/BugzillaIssueTrackingPlugin BugzillaIssueTrackingPlugin] :: integrates Bugzilla into Trac keeping TracLinks 
    420 
    521Ticket 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. 
    … …  
    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://trac.edgewall.org/browser/trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution. 
    45  
    46 See #Trac3521 for an updated sourceforge2trac script. 
     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 
    4764 
    4865== Mantis == 
    4966 
    50 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 
    51  
    52 Mantis bugs can be imported using the attached script. 
    53  
    54 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: 
    5568  * bugs 
    5669  * bug comments 
    5770  * bug activity (field changes) 
    58   * 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) . 
    5972 
    60 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 == 
    6174 
    62 mantis2trac.py has the same parameters as the bugzilla2trac.py script: 
    63 {{{ 
    64 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.  
    6576 
    66 Usage: mantis2trac.py [options]  
     77== Scarab == 
    6778 
    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 
     80    * Requires [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] 
    7681 
    77 Additional configuration options can be defined directly in the script. 
    78 }}}  
     82== Sourceforge == 
    7983 
    80 == Jira == 
     84 [http://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript] :: importer of !SourceForge's new backup file (originated from #Trac3521) 
    8185 
    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 
     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. 
    8987 
    9088== Other == 
    … …  
    9290Since 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. 
    9391 
    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) 
     92=== Comma delimited file - CSV === 
     93See [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) 
    9694Comments 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.  
    9795 
    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  
     96---- 
     97See also:  
     98 * to import/export wiki pages: TracAdmin,  
     99 * to export tickets: TracTickets, TracQuery