Changes between Version 7 and Version 8 of TracImport


Ignore:
Timestamp:
Dec 14, 2014, 5:16:20 PM (9 years ago)
Author:
trac
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • TracImport

    v7 v8  
    11= Importing ticket data =
    2 [[PageOutline]]
    3 
    4 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.
    5 
    6 Below, 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.
    162
    173== Bugzilla ==
    18 
    19  th:BugzillaIssueTrackingPlugin:: integrates Bugzilla into Trac keeping TracLinks
    204
    215Ticket 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.
    … …  
    5640For more details on the available options, see the configuration section at the top of the script.
    5741
    58 == Jira ==
     42== Sourceforge ==
    5943
    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
     44Ticket 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
     46See #Trac3521 for an updated sourceforge2trac script.
    6447
    6548== Mantis ==
    6649
    67  th:MantisImportScript:: script to import from Mantis into Trac the following data:
     50The 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
     52Mantis bugs can be imported using the attached script.
     53
     54Currently, the following data is imported from Mantis:
    6855  * bugs
    6956  * bug comments
    7057  * bug activity (field changes)
    71   * attachments (as long as the files live in the mantis db, not on the filesystem) .
     58  * attachments (as long as the files live in the mantis db, not on the filesystem)
    7259
    73 == !PlanetForge ==
     60If 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.
    7461
    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.
     62mantis2trac.py has the same parameters as the bugzilla2trac.py script:
     63{{{
     64mantis2trac - Imports a bug database from Mantis into Trac.
    7665
    77 == Scarab ==
     66Usage: mantis2trac.py [options]
    7867
    79  th:ScarabToTracScript:: script that migrates Scarab issues to Trac tickets
    80     * Requires [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]
     68Available 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
    8176
    82 == Sourceforge ==
     77Additional configuration options can be defined directly in the script.
     78}}}
    8379
    84  th:SfnToTracScript:: importer of !SourceForge's new backup file (originated from #Trac3521)
     80== Jira ==
    8581
    86 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.
     82The [http://trac-hacks.org/wiki/JiraToTracIntegration Jira2Trac plugin] provides you with tools to import Atlassian Jira backup files into Trac.
     83
     84The 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
    8789
    8890== Other ==
    … …  
    9092Since 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.
    9193
    92 === Comma delimited file - CSV ===
     94=== Using a comma delimited file - CSV ===
    9395See [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)
    94 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.
    9596
    96 ----
    97 See also:
    98  * to import/export wiki pages: TracAdmin,
    99  * to export tickets: TracTickets, TracQuery