id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,branch,changelog,apichanges,internalchanges 7340,"[PATCH] bugzilla2trac.py: work with bugzilla 2.16.7, use bugzilla severities as trac priorities",jholg@…,Jeroen Ruigrok van der Werven,"Just managed to import my Bugzilla 2.16.7 bugs into the Trac ticket system. I had to patch bugzilla2trac.py: 1. Defect: to work with the 2.16.7 bugzilla db layout, which seems to use * product.product rather than product.name (table product) * bugs.product rather that bugs.product_id (table bugs) * bugs.component rather than bugs.component_id (table bugs) * components.value rather than components.id (table components) 1. Enhancement: to allow for importing the Bugzilla severities as Trac priorities, and forget about the Bugzilla priorities completely; just like the default out-of-the box trac ticket system ""simple setup"" these days (no severities, but priorities ''instead''). I added a new command line parameter ['-n', '--noseverities'] to switch on the latter. Note1: The patch is based on bugzilla2trac.py in Revision 6820, as downloaded from trac.edgewall.org. Note2: This has only been tested with my pretty simple setup (single bugzilla product, COMPONENTS_FROM_PRODUCTS = False, custom LOGIN_MAP), and only against Bugzilla 2.16.7 Holger (Patch attached)",defect,closed,normal,0.12,ticket system,0.11b2,normal,fixed,patch bugzilla,,,,,