Legend:

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.

6

7

{{{

8

$ bugzilla2trac.py

9

bugzilla2trac - Imports a bug database from Bugzilla into Trac.

10

11

Usage: bugzilla2trac.py [options]

12

13

Available Options:

14

--db <MySQL dbname> - Bugzilla's database

15

--tracenv /path/to/trac/env - full path to Trac db environment

16

-h | --host <MySQL hostname> - Bugzilla's DNS host name

17

-u | --user <MySQL username> - effective Bugzilla's database user

18

-p | --passwd <MySQL password> - Bugzilla's user password

19

-c | --clean - remove current Trac tickets before importing

20

--help | help - this help info

21

22

Additional configuration options can be defined directly in the script.

23

}}}

24

25

Currently, the following data is imported from Bugzilla:

26

27

* bugs

28

* bug activity (field changes)

29

* bug attachments

30

* user names and passwords (put into a htpasswd file)

31

32

The script provides a number of features to ease the conversion, such as:

33

34

* PRODUCT_KEYWORDS: Trac doesn't have the concept of products, so the script provides the ability to attach a ticket keyword instead.

* 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.

39

40

For more details on the available options, see the configuration section at the top of the script.

41

42

== Sourceforge ==

43

44

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.

45

46

== Mantis ==

47

48

NB! 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

49

50

Mantis bugs can be imported using the attached script.

51

52

Currently, the following data is imported from Mantis:

53

* bugs

54

* bug comments

55

* bug activity (field changes)

56

* attachments (as long as the files live in the mantis db, not on the filesystem)

57

58

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.

59

60

mantis2trac.py has the same parameters as the bugzilla2trac.py script:

61

{{{

62

mantis2trac - Imports a bug database from Mantis into Trac.

63

64

Usage: mantis2trac.py [options]

65

66

Available Options:

67

--db <MySQL dbname> - Mantis database

68

--tracenv /path/to/trac/env - Full path to Trac db environment

69

-h | --host <MySQL hostname> - Mantis DNS host name

70

-u | --user <MySQL username> - Effective Mantis database user

71

-p | --passwd <MySQL password> - Mantis database user password

72

-c | --clean - Remove current Trac tickets before importing

73

--help | help - This help info

74

75

Additional configuration options can be defined directly in the script.

76

}}}

77

78

== Other ==

79

80

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.

81

82

=== Using a comma delimited file - CSV ===

83

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)