close Warning: Can't synchronize with repository "(default)" (The repository directory has changed, you should resynchronize the repository with: trac-admin $ENV repository resync '(default)'). Look in the Trac log for more information.

Changes between Version 1 and Version 2 of TracImport


Ignore:
Timestamp:
2011-07-31T04:33:06-07:00 (13 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracImport

    v1 v2  
    33== Bugzilla ==
    44
    5 Ticket data can be imported from Bugzilla using the [http://projects.edgewall.com/trac/browser/trunk/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the contrib/ directory of the Trac distribution.
     5Ticket 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.
    66
    77{{{
     
    4242== Sourceforge ==
    4343
    44 Ticket data can be imported from Sourceforge using the [http://projects.edgewall.com/trac/browser/trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution.
     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.
    4547
    4648== Mantis ==
     49
     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
    4751
    4852Mantis bugs can be imported using the attached script.
     
    5256  * bug comments
    5357  * bug activity (field changes)
     58  * attachments (as long as the files live in the mantis db, not on the filesystem)
    5459
    55 Attachments are NOT imported.  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.
     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.
    5661
    5762mantis2trac.py has the same parameters as the bugzilla2trac.py script:
     
    7378}}}
    7479
     80== Jira ==
     81
     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
     89
    7590== Other ==
    7691
     
    7994=== Using a comma delimited file - CSV ===
    8095See [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)
     96Comments 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.
     97
     98=== Using an Excel (.xls) or comma delimited file (.csv) ===
     99This 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
     101You 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
     103This 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
     105Based on the ticket id (or, if no id exists, on the summary) in the imported file, tickets are either created or updated.
     106
     107