Changes between Version 2 and Version 3 of TracImport

Timestamp:

Nov 9, 2012, 9:15:32 AM (12 years ago)

Author:

trac

Comment:

--

TracImport

@@ -1 +1 @@
 = Importing ticket data =
+[[PageOutline]]
+
+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.
+
+Below, follows a collection of some of those.
+
+== !TicketImportPlugin ==
+
+ [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'''. 
+
+== !ExportImportXlsPlugin ==
+
+ [http://trac-hacks.org/wiki/ExportImportXlsPlugin ExportImportXlsPlugin] :: this plug-in add an admin panel for export and import tickets via '''XLS file'''.
+  * It depends on the python packages xlwt/rxld.
 
 == Bugzilla ==
+
+ [http://trac-hacks.org/wiki/BugzillaIssueTrackingPlugin BugzillaIssueTrackingPlugin] :: integrates Bugzilla into Trac keeping TracLinks
 
 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.
 
-== Sourceforge ==
+== Jira ==
 
-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.
-
-See #Trac3521 for an updated sourceforge2trac script.
+ [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:
+   - Parses the Jira backup XML file
+   - Sends the imported Jira data and attachments to Trac using the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]
+   - Generates a htpasswd file containing the imported Jira users and their SHA-512 base64 encoded passwords
 
 == Mantis ==
 
-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
-
-Mantis bugs can be imported using the attached script.
-
-Currently, the following data is imported from Mantis:
+ [http://trac-hacks.org/wiki/MantisImportScript MantisImportScript] :: script to import from Mantis into Trac the following data:
   * bugs
   * bug comments
   * bug activity (field changes)
-  * attachments (as long as the files live in the mantis db, not on the filesystem) 
+  * attachments (as long as the files live in the mantis db, not on the filesystem) .
 
-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.
+== !PlanetForge ==
 
-mantis2trac.py has the same parameters as the bugzilla2trac.py script:
-{{{
-mantis2trac - Imports a bug database from Mantis into Trac.
+ [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. 
 
-Usage: mantis2trac.py [options] 
+== Scarab ==
 
-Available Options:
-  --db <MySQL dbname>              - Mantis database
-  --tracenv /path/to/trac/env      - Full path to Trac db environment
-  -h | --host <MySQL hostname>     - Mantis DNS host name
-  -u | --user <MySQL username>     - Effective Mantis database user
-  -p | --passwd <MySQL password>   - Mantis database user password
-  -c | --clean                     - Remove current Trac tickets before importing
-  --help | help                    - This help info
+ [http://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript] :: script that migrates Scarab issues to Trac tickets
+    * Requires [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]
 
-Additional configuration options can be defined directly in the script.
-}}} 
+== Sourceforge ==
 
-== Jira ==
+ [http://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript] :: importer of !SourceForge's new backup file (originated from #Trac3521)
 
-The [http://trac-hacks.org/wiki/JiraToTracIntegration Jira2Trac plugin] provides you with tools to import Atlassian Jira backup files into Trac.
-
-The plugin consists of a Python 3.1 commandline tool that:
-
- - Parses the Jira backup XML file
- - Sends the imported Jira data and attachments to Trac using the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]
- - Generates a htpasswd file containing the imported Jira users and their SHA-512 base64 encoded passwords
+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.
 
 == Other ==
@@ -92 +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.
 
-=== Using a comma delimited file - CSV ===
-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)
+=== Comma delimited file - CSV ===
+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)
 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. 
 
-=== Using an Excel (.xls) or comma delimited file (.csv) ===
-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.
-
-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.
-
-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.
-
-Based on the ticket id (or, if no id exists, on the summary) in the imported file, tickets are either created or updated. 
-
-
+----
+See also: 
+ * to import/export wiki pages: TracAdmin, 
+ * to export tickets: TracTickets, TracQuery