43 | | Ticket data can be imported from Sourceforge using the sourceforge2trac.py script, available in the contrib/ directory of the Trac distribution. |
| 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. |
| 45 | |
| 46 | == Mantis == |
| 47 | |
| 48 | Mantis bugs can be imported using the attached script. |
| 49 | |
| 50 | Currently, the following data is imported from Mantis: |
| 51 | * bugs |
| 52 | * bug comments |
| 53 | * bug activity (field changes) |
| 54 | |
| 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. |
| 56 | |
| 57 | mantis2trac.py has the same parameters as the bugzilla2trac.py script: |
| 58 | {{{ |
| 59 | mantis2trac - Imports a bug database from Mantis into Trac. |
| 60 | |
| 61 | Usage: mantis2trac.py [options] |
| 62 | |
| 63 | Available Options: |
| 64 | --db <MySQL dbname> - Mantis database |
| 65 | --tracenv /path/to/trac/env - Full path to Trac db environment |
| 66 | -h | --host <MySQL hostname> - Mantis DNS host name |
| 67 | -u | --user <MySQL username> - Effective Mantis database user |
| 68 | -p | --passwd <MySQL password> - Mantis database user password |
| 69 | -c | --clean - Remove current Trac tickets before importing |
| 70 | --help | help - This help info |
| 71 | |
| 72 | Additional configuration options can be defined directly in the script. |
| 73 | }}} |
| 74 | |
| 75 | == Other == |
| 76 | |
| 77 | 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. |