id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,branch,changelog,apichanges,internalchanges 7333,[PATCH] bugzilla2trac.py: import Bugzilla version 2.18.4,thomas.klenner@…,,"I just managed to import my bugs from Bugzilla version 2.18.4 into Trac Version 0.10.4. However, some changes were necessary to the original Bugzilla DB contents as well as to the import script itself: == Trac needs unique product names == I used the option in the conversion script: {{{ COMPONENTS_FROM_PRODUCTS = False }}} This caused the script to fail because my Bugzilla DB contained the same component name for various products. After renaming the duplicate components, the script managed to import them. == DB schema problem == The import of attachments failed because of a wrong check for the Bugzilla version in the script (line 824): The correct select statement from tables attachments and attach_data depends on the Bugzilla version. The script uses the table attach_data for versions greater or equal than 2180. However, this table was introduced in version 2211 (see http://www.ravenbrook.com/project/p4dti/tool/cgi/bugzilla-schema/). After changing the condition to {{{ if BZ_VERSION >= 2210: }}} the import succeeded. == Multiple attachments.isobsolete at the same time == My bugzilla DB contained three changes of type ""attachments.isobsolete"" for the same bug at the same time. This caused a duplicate primary key error in table ticket_change. See my comments on Ticket #6753 for details. ",defect,closed,normal,,contrib,0.10.4,normal,wontfix,"verify, patch, bugzilla2trac",,,,,