source: wiki/pages/TracImport @ 43267

Last change on this file since 43267 was 40558, checked in by obi, 2 years ago

reset wiki

File size: 5.4 KB
Line 
1= Importing ticket data =
2[[PageOutline]]
3
4To migrate issue tickets from other issue-tracking systems or perform housekeeping actions on tickets or simply synchronize different databases, there are some tools, plug-ins and scripts available, which let you import or update tickets into Trac.
5
6== !TicketImportPlugin ==
7
8[http://trac-hacks.org/wiki/TicketImportPlugin TicketImportPlugin]: this plug-in lets you import or update 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 spreadsheet'''.
9
10== !ExportImportXlsPlugin ==
11
12[http://trac-hacks.org/wiki/ExportImportXlsPlugin ExportImportXlsPlugin]: this plug-in adds an admin panel for exporting and importing tickets via '''XLS file'''. Requires the python packages xlwt/rxld.
13
14== Bugzilla ==
15
16[http://trac-hacks.org/wiki/BugzillaIssueTrackingPlugin BugzillaIssueTrackingPlugin]: 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.
17
18{{{
19$ bugzilla2trac.py
20bugzilla2trac - Imports a bug database from Bugzilla into Trac.
21
22Usage: bugzilla2trac.py [options]
23
24Available Options:
25  --db <MySQL dbname>              - Bugzilla's database
26  --tracenv /path/to/trac/env      - full path to Trac db environment
27  -h | --host <MySQL hostname>     - Bugzilla's DNS host name
28  -u | --user <MySQL username>     - effective Bugzilla's database user
29  -p | --passwd <MySQL password>   - Bugzilla's user password
30  -c | --clean                     - remove current Trac tickets before importing
31  --help | help                    - this help info
32
33Additional configuration options can be defined directly in the script.
34}}}
35
36Currently, the following data is imported from Bugzilla:
37  * bugs
38  * bug activity (field changes)
39  * bug attachments
40  * user names and passwords (put into a htpasswd file)
41
42The script provides a number of features to ease the conversion, such as:
43  * PRODUCT_KEYWORDS: Trac has no concept of products, so the script provides the ability to attach a ticket keyword instead.
44  * IGNORE_COMMENTS: Don't import Bugzilla comments that match a certain regexp.
45  * 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.
46
47For more details on the available options, see the configuration section at the top of the script.
48
49=== Known Issues ===
50{{{
51#!comment
52                   Don't merge this section in the default page
53}}}
54[[TicketQuery(keywords=~bugzilla,status=!closed)]]
55
56The 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.
57
58== Jira ==
59
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.
64
65== Mantis ==
66
67[http://trac-hacks.org/wiki/MantisImportScript MantisImportScript]: script to import the following data from Mantis into Trac:
68  * bugs
69  * bug comments
70  * bug activity (field changes)
71  * attachments (as long as the files live in the mantis db, not on the filesystem) .
72
73== !PlanetForge ==
74
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. Has no 'import' feature.
76
77== Scarab ==
78
79[http://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript]: script that migrates Scarab issues to Trac tickets. Requires [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]
80
81== Sourceforge ==
82
83[http://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript]: importer of !SourceForge's new backup file (originated from #Trac3521).
84Also, 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.
85
86== Other ==
87
88Since 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.
89
90=== Comma delimited file - CSV ===
91See [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.
92Comments 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.
93
94----
95See also:
96 * to import/export wiki pages: TracAdmin,
97 * to export tickets: TracTickets, TracQuery
Note: See TracBrowser for help on using the repository browser.