Changes between Version 1 and Version 2 of TracImport

Timestamp:

Apr 3, 2020, 9:27:33 PM (5 years ago)

Author:

trac

Comment:

--

TracImport

@@ -1 @@
-= Importing ticket data =
+= Importing ticket data
 
-== Bugzilla ==
+[[PageOutline(2-5,Contents,pullout)]]
 
-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.
+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. 
+
+== !TicketImportPlugin
+
+[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'''. 
+
+== !ExportImportXlsPlugin
+
+[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.
+
+== Bugzilla
+
+[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.
 
 {{{
@@ -24 +36 @@
 
 Currently, the following data is imported from Bugzilla:
-
-  * bugs
-  * bug activity (field changes)
-  * bug attachments
-  * user names and passwords (put into a htpasswd file)
+ * bugs
+ * bug activity (field changes)
+ * bug attachments
+ * user names and passwords (put into a htpasswd file)
 
 The script provides a number of features to ease the conversion, such as:
-
-  * PRODUCT_KEYWORDS:  Trac doesn't have the concept of products, so the script provides the ability to attach a ticket keyword instead.
-
-  * IGNORE_COMMENTS:  Don't import Bugzilla comments that match a certain regexp.
-
-  * 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.
+ * PRODUCT_KEYWORDS: Trac has no concept of products, so the script provides the ability to attach a ticket keyword instead.
+ * IGNORE_COMMENTS: Don't import Bugzilla comments that match a certain regexp.
+ * 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.
 
 For more details on the available options, see the configuration section at the top of the script.
 
-== Sourceforge ==
+=== Known Issues
+{{{#!comment
+Don't merge this section in the default page
+}}}
+[[TicketQuery(keywords=~bugzilla,status=!closed)]]
 
-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.
+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.
 
-See #Trac3521 for an updated sourceforge2trac script.
+== Jira
 
-== Mantis ==
+[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:
+ - Parses the Jira backup XML file.
+ - Sends the imported Jira data and attachments to Trac using the [th:XmlRpcPlugin].
+ - Generates a htpasswd file containing the imported Jira users and their SHA-512 base64 encoded passwords.
 
-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
 
-Mantis bugs can be imported using the attached script.
+[https://trac-hacks.org/wiki/MantisImportScript MantisImportScript]: a script to import the following type of data from Mantis into Trac:
+ * bugs
+ * bug comments
+ * bug activity (field changes)
+ * attachments (as long as the files live in the mantis database, not on the filesystem).
 
-Currently, the following data is imported from Mantis:
-  * bugs
-  * bug comments
-  * bug activity (field changes)
-  * attachments (as long as the files live in the mantis db, not on the filesystem) 
+== !PlanetForge
 
-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.
+[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. 
 
-mantis2trac.py has the same parameters as the bugzilla2trac.py script:
-{{{
-mantis2trac - Imports a bug database from Mantis into Trac.
+== Scarab
 
-Usage: mantis2trac.py [options] 
+[https://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript]: a script that migrates Scarab issues to Trac tickets. Requires [th:XmlRpcPlugin].
 
-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
+== Sourceforge
 
-Additional configuration options can be defined directly in the script.
-}}} 
+[https://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript]: importer of !SourceForge's new backup file (originated from #Trac3521).
+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.
 
-== Jira ==
+== Other
 
-The [http://trac-hacks.org/wiki/JiraToTracIntegration Jira2Trac plugin] provides you with tools to import Atlassian Jira backup files into Trac.
+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.
 
-The plugin consists of a Python 3.1 commandline tool that:
+=== Comma delimited file - CSV
 
- - 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
+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.
 
-== Other ==
+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. 
 
-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)
-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