Table/Field exists in bugzilla_3 but not in bugzilla_2_18

Table/Field exists in bugzilla_2_18 but not in bugzilla_3

New Field in bugzilla_3 that is set to NOT NULL

Format 2.18/3 => Similar Fields Between Bugzilla_2_18 and Bugzilla_3 but have different attributes

NAME	attach_data
TYPE	TABLE
DESCRIPTION	!! table found in bugzilla_3 but not in bugzilla_2_18 !!
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	MEDIUMINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
thedata	LONGBLOB		NO		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	attachments
TYPE	TABLE
DESCRIPTION	Users can upload attachments to bugs. An attachment can be marked as a patch. Attachments are stored in the attachments table
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
attach_id	MEDIUMINT		NO	PRI	a unique ID
bug_id	MEDIUMINT		NO	MUL	the bug to which this is attached (foreign key bugs.bug_id)
creation_ts	DATETIME		NO	MUL	the creation time
modification_time	DATETIME		YES	MUL	!! field in bugzilla_3 and not in bugzilla_2.18 !!
description	MEDIUMTEXT		NO		a description of the attachment
mimetype	MEDIUMTEXT		NO		the MIME type of the attachment
ispatch	TINYINT		YES		non-zero if this attachment is a patch file
filename	VARCHAR		NO		the filename of the attachment
submitter_id	MEDIUMINT		NO	MUL	the userid of the attachment (foreign key profiles.userid)
isobsolete	TINYINT		NO		Non-zero if this attachment is marked as
isprivate	TINYINT		NO		Non-zero if this attachment is private
isurl	TINYINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
it_id	TINYINT		YES		the id of an attachment in IssueTracker which is a separate system, it allows a bug report to show Bugzillla attachments and IssueTracker attachments in the same list
thedata	longblob		NO		!! field in bugzilla_2.18 but not in bugzilla_3 !!

NAME	bug_group_map
TYPE	TABLE
DESCRIPTION	Which bugs are in which groups.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
bug_id	MEDIUMINT		NO	PRI	The id of a bug that belongs to some group (foreign key bugs.bug_id)
group_id	MEDIUMINT		NO	PRI	The group id (foreign key groups.id)

NAME	bug_severity
TYPE	TABLE
DESCRIPTION	The severity values of bugs
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	SMALLINT		NO	PRI	a unique ID
value	VARCHAR		NO	UNI	A possible value of the field
sortkey	SMALLINT		YES	MUL	!! field in bugzilla_3 and not in bugzilla_2.18 !!
isactive	TINYINT	1	YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	bug_status
TYPE	TABLE
DESCRIPTION	The status values of bugs
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	SMALLINT		NO	PRI	a unique ID
value	VARCHAR		NO	UNI	A possible value of the field
sortkey	SMALLINT		NO	/MUL	A number used to determine the order in which values are shown
isactive	TINYINT	1	NO		1 if this value is available in the user interface 0 otherwise
is_open	TINYINT	1	NO		if the bug status is an open state
description	MEDIUMTEXT		NO		bug status description

NAME	bugs
TYPE	TABLE
DESCRIPTION	The bugs themselves.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
bug_id	MEDIUMINT		NO	PRI	bug ID
assigned_to	MEDIUMINT		NO	MUL	The current owner of the bug (foreign key profiles.userid)
bug_file_loc	text/MEDIUMTEXT		YES		A URL which points to more information about the bug
bug_severity	VARCHAR		NO	MUL	the severity value of a bug. foreign key bug_severity.value
bug_status	VARCHAR		NO	MUL	The workflow status of the bug. foreign key
creation_ts	DATETIME		NO	MUL	The times of the bug creation
delta_ts	timestamp/DATETIME		NO	MUL	The timestamp of the last update. This includes updates to some related tables
short_desc	MEDIUMTEXT		NO		A short description of the bug
op_sys	VARCHAR		NO	MUL	The operating system on which the bug was observed. foreign key op_sys.value
priority	VARCHAR		NO	MUL	The priority of the bug. foreign key priority.value
product_id	SMALLINT		NO	MUL	The product (foreign key products.id)
rep_platform	VARCHAR		NO		The platform on which the bug was reported. foreign key rep_platform.value
reporter	MEDIUMINT		NO	MUL	The user who reported this (foreign key profiles.userid)
version	VARCHAR		NO	MUL	The product version (foreign key versions.value)
component_id	MEDIUMINT		NO	MUL	The product component (foreign key components.id)
resolution	VARCHAR		YES	MUL	The bug resolution foreign key resolution.value
target_milestone	VARCHAR	---	NO	MUL	The milestone by which this bug should be resolved. (foreign key milestones.value)
qa_contact	MEDIUMINT		YES	MUL	The QA contact (foreign key profiles.userid)
status_whiteboard	MEDIUMTEXT		YES/NO		This seems to be just a small whiteboard field
votes	MEDIUMINT		YES	MUL	The number of votes
keywords	MEDIUMTEXT		YES		A set of keywords. Note that this duplicates information in the keywords table.(foreign key keyworddefs.name)
lastdiffed	DATETIME		YES		The time at which information about this bug changing was last emailed to the cc list
everconfirmed	TINYINT		NO		1 if this bug has ever been confirmed. This is used for validation of some sort
reporter_accessible	TINYINT	1	NO		1 if the reporter can see this bug (even if in the wrong group) 0 otherwise
cclist_accessible	TINYINT	1	NO		1 if people on the CC list can see this bug (even if in the wrong group);0 otherwise
estimated_time	DECIMAL	/0.00	2)"/NO		The original estimate of the total effort required to fix this bug (in hours)
remaining_time	DECIMAL	/0.00	2)"/NO		The current estimate of the remaining effort required to fix this bug (in hours)
deadline	DATETIME		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
alias	VARCHAR		YES	/UNI	An alias for the bug which can be used instead of the bug number.
cust_facing	VARCHAR		YES		used to mark extra status information in bug reports and is used by certain groups
devel_whiteboard	VARCHAR		YES		used to mark extra status information in bug reports and used by devel group
fixed_in	VARCHAR		YES		it is a text field to enter version that a bug has been fixed in, it is not strictly enforced, (examples: rpm package version, a release version)
internal_whiteboard	VARCHAR		YES		used to mark extra status information in bug reports and used by bz group
qa_whiteboard	VARCHAR		YES		used to mark extra status information in bug reports and used by qa group

NAME	bugs_activity
TYPE	TABLE
DESCRIPTION	Activity on the bugs table.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
bug_id	MEDIUMINT		NO	MUL	Which bug (foreign key bugs.bug_id)
attach_id	MEDIUMINT		YES	MUL	If the change was to an attachment (foreign key attachments.attach_id)
who	MEDIUMINT		NO	MUL	Which user (foreign key profiles.userid)
bug_when	DATETIME		NO	MUL	When was the change made?
fieldid	MEDIUMINT		NO	MUL	What was the fieldid? (foreign key fielddefs.id)
added	VARCHAR		YES		The new value of this field
removed	VARCHAR		YES		The old value of this field

NAME	bz_it_map
TYPE	TABLE
DESCRIPTION	Mapping bugzilla bug ids with issue tracker ids.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
bz_id	MEDIUMINT		NO	PRI/MUL	Bugzilla bug id (foreign key bugs.bug_id)
it_id	MEDIUMINT		NO		Issue tracker id
it_score	MEDIUMINT		NO		Issue tracker score

NAME	bz_schema
TYPE	TABLE
DESCRIPTION	!! table found in bugzilla_3 but not in bugzilla_2_18 !!
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
schema_data	LONGBLOB		NO		!! field in bugzilla_3 and not in bugzilla_2.18 !!
version	DECIMAL		NO		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	category_group_map
TYPE	TABLE
DESCRIPTION	Which groups does a user have to be in to view chart data in a given category.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
category_id	SMALLINT		NO	PRI	The series category (foreign key series_categories.id)
group_id	MEDIUMINT		NO	PRI	Users who have asked to receive email when a bug changes (foreign key groups.id)

NAME	cc
TYPE	TABLE
DESCRIPTION	Users who have asked to receive email when a bug changes.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
bug_id	MEDIUMINT		NO	PRI	The bug (foreign key bugs.bug_id)
who	MEDIUMINT		NO	PRI	The user (foreign key profiles.userid)

NAME	classifications
TYPE	TABLE
DESCRIPTION	!! table found in bugzilla_3 but not in bugzilla_2_18 !!
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	SMALLINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
name	VARCHAR		NO	UNI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
description	MEDIUMTEXT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
sortkey	SMALLINT		NO		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	component_cc
TYPE	TABLE
DESCRIPTION	Maps every component to its users in the cclist, one user per record
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
user_id	MEDIUMINT		YES/NO	MUL/PRI	The user id (foreign key profiles.userid)
component_id	MEDIUMINT		NO	MUL/PRI	The component id (foreign key components.id)

NAME	components
TYPE	TABLE
DESCRIPTION	the work for each product is divided into the components of that product, each component is represented by a row in the componenets table
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	MEDIUMINT		NO	PRI	The component id.
name	VARCHAR		NO	MUL	The component name
product_id	SMALLINT		NO	MUL	The product (foreign key products.id)
initialowner	MEDIUMINT		NO	MUL	The default initial owner of bugs in this component. On component creation (foreign key profiles.userid)
initialqacontact	MEDIUMINT		YES	MUL	The initial qa_contact field for bugs of this component. Note that the use of the qa_contact field is optional (foreign key profiles.userid)
description	MEDIUMTEXT		NO		A description of the component.
initialcclist	MEDIUMTEXT		YES		is a string data type with a ':' separated list of bugzilla user id's to allow multiple people to automatically get cc'ed when bugs were created for a componet

NAME	dependencies
TYPE	TABLE
DESCRIPTION	Which bugs depend on other bugs.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
blocked	MEDIUMINT		NO	MUL	Which bug is blocked (foreign key bugs.bug_id)
dependson	MEDIUMINT		NO	MUL	Which bug does it depend on (foreign key bugs.bug_id)

NAME	duplicates
TYPE	TABLE
DESCRIPTION	Which bugs are duplicates of which other bugs.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
dupe_of	MEDIUMINT		NO	MUL	The bug which is duplicated (foreign key bugs.bug_id)
dupe	MEDIUMINT		NO	PRI	The duplicate bug (foreign key bugs.bug_id)

NAME	email_setting
TYPE	TABLE
DESCRIPTION	!! table found in bugzilla_3 but not in bugzilla_2_18 !!
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
user_id	MEDIUMINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
relationship	TINYINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
event	TINYINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	ext_bz_bug_map
TYPE	TABLE
DESCRIPTION	has the links of our bug ids to external bug ids to that allow bugzilla ids to have references to external bugs in outside bug trackers
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
bug_id	MEDIUMINT		NO	PRI/MUL	bugzilla bug id (foreign key bugs.bug_id)
ext_bz_id	MEDIUMINT		NO	PRI/MUL	id for external bugzilla (foreign key external_bugzilla.id)
ext_bz_bug_id	MEDIUMINT		NO		external bugzilla bug id

NAME	external_bugzilla
TYPE	TABLE
DESCRIPTION	lists the trackers we know about
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	MEDIUMINT		NO	PRI	the tracker id
url	VARCHAR		NO		the url of the tracker
description	VARCHAR		NO		description of the tracker
full_url	VARCHAR		YES		the full url of the tracker
is_bz	TINYINT		YES		is it a bugzilla tracker

NAME	fielddefs
TYPE	TABLE
DESCRIPTION	The fields of a bug.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	MEDIUMINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
name	VARCHAR		NO	UNI	field name or definition (some fields are names of other tables or of fields in other tables)
type	SMALLINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
custom	TINYINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
description	mediumtext/TINYTEXT		NO		long description
mailhead	TINYINT		NO		whether or not to send the field description in mail notifications.
sortkey	SMALLINT		NO	MUL	the order of fields in mail notifications.
obsolete	TINYINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
enter_bug	TINYINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
fieldid	mediumint(9)		NO	PRI	!! field in bugzilla_2.18 but not in bugzilla_3 !!

NAME	flagexclusions
TYPE	TABLE
DESCRIPTION	It may be forbidden to set a given flag on an item (bug or attachment) if that item is in a given product or component. This table records such exclusions.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
type_id	SMALLINT		NO	MUL	The flag type. (foreign key flagtypes.id)
product_id	SMALLINT		YES	MUL	The product (foreign key products.id)
component_id	MEDIUMINT		YES	MUL	The component (foreign key components.id)

NAME	flaginclusions
TYPE	TABLE
DESCRIPTION	An item (bug or attachment) may be required to be in a given product or component for a flag to be set. This table records such requirements.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
type_id	SMALLINT		NO	MUL	The flag type. (foreign key flagtypes.id)
product_id	SMALLINT		YES	MUL	The product (foreign key products.id)
component_id	MEDIUMINT		YES	MUL	The component (foreign key components.id)

NAME	flags
TYPE	TABLE
DESCRIPTION	This table records the flags set on bugs or attachments.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	MEDIUMINT		NO	PRI	A unique ID.
type_id	SMALLINT		NO	MUL	The flag type. (foreign key flagtypes.id)
status	CHAR		NO		+ (granted)
bug_id	MEDIUMINT		NO	MUL	bug. (foreign key bugs.bug_id)
attach_id	MEDIUMINT		YES	MUL	The attachment (foreign key attachments.attach_id)
creation_date	DATETIME		NO		The date the flag was created.
modification_date	DATETIME		YES		The date the flag was most recently modified or created
setter_id	MEDIUMINT		YES	MUL	The ID of the user who created (foreign key profiles.userid)
requestee_id	MEDIUMINT		YES	MUL	The ID of the user to whom this request flag is addressed (foreign key profiles.userid)
is_active	TINYINT	1	NO		when a flag is created for the first time on a bug report is_active is set to 1 when the flag is deleted, the row is not really deleted, the is_active value is set to 0,if a flag is then reinstated later for a bug, it just gets is_active reset to 1 again

NAME	flagtypes
TYPE	TABLE
DESCRIPTION	The types of flags available for bugs and attachments. See the notes on flags.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	SMALLINT		NO	PRI	The flag type ID
name	VARCHAR		NO		The short flag name
description	text/MEDIUMTEXT		YES/NO		The description of the flag
cc_list	VARCHAR		YES		A string containing email addresses to which notification of requests for this flag should be sent. This is filtered using the groups system before messages are actually sent
target_type	CHAR	b	NO		type for attachment flags
is_active	TINYINT	1	NO		1 if the flag appears in the UI and can be set; 0 otherwise.
is_requestable	TINYINT		NO		1 if the flag may be requested; 0 otherwise.
is_requesteeble	TINYINT		NO		1 if a request for this flag may be aimed at a particular user; 0 otherwise
is_multiplicable	TINYINT		NO		1 if multiple instances of this flag may be set on the same item; 0 otherwise.
sortkey	SMALLINT		NO		An integer used for sorting flags for display.
grant_group_id	MEDIUMINT		YES	MUL	Group membership required to grant this flag. (foreign key groups.id)
request_group_id	MEDIUMINT		YES		Group membership required to request this flag. (foreign key groups.id)
view_group_id	MEDIUMINT		YES	MUL	corresponds to the groups table id designating which group a person needs to be in to see that flag choice in a bug report (foreign key groups.id)

NAME	group_control_map
TYPE	TABLE
DESCRIPTION	This table describes the relationship of groups to products (whether membership in a given group is required for entering or editing a bug in a given product).
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
group_id	MEDIUMINT		NO	PRI	The group. (foreign key groups.id)
product_id	SMALLINT		NO	PRI	The product. (foreign key products.id)
entry	TINYINT		NO		1 if membership of this group is required to enter a bug in this product; 0 otherwise.
membercontrol	TINYINT		NO		Determines what control members of this group have over whether a bug for this product is placed in this group
othercontrol	TINYINT		NO		Determines what control non-group-members have over whether a new bug for this product is placed in this group.
canedit	TINYINT		NO		1 if membership of this group is required to edit a bug in this product; 0 otherwise.
editcomponents	TINYINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
editbugs	TINYINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
canconfirm	TINYINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	group_group_map
TYPE	TABLE
DESCRIPTION	Groups can be configured such that membership of one group automatically confers rights over some other groups. This table records that configuration
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
member_id	MEDIUMINT		NO	PRI/MUL	The group whose membership grants membership or bless privilege for another group (foreign key groups.id)
grantor_id	MEDIUMINT		NO	PRI/MUL	The group whose membership or bless privilege is automatically granted.(foreign key groups.id)
grant_type	TINYINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
isbless	TINYINT		NO		is set to 1 or 0 based on whether people belonging to that group can bless others into that group gives them admin rights to put people in that group

NAME	groups
TYPE	TABLE
DESCRIPTION	This table describes a number of user groups. Each group allows its members to perform a restricted activity.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	MEDIUMINT		NO	PRI	The group id.
name	VARCHAR		NO	UNI	A short name for the group.
description	text/MEDIUMTEXT		NO		A long description of the group.
isbuggroup	TINYINT		NO		1 if this is a group controlling access to a set of bugs.
userregexp	VARCHAR		YES		a regexp used to determine membership of new users.
isactive	TINYINT	1	NO		1 if bugs can be added to this group; 0 otherwise.
icon_url	TINYTEXT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
contract	TINYINT		YES		remnants of an old RH feature where a group was designated
last_changed	DATETIME		NO		the date when a group had its attributes changed last, BZ uses the date to determine whether a persons groups permissions needs to be re-assessed or re-derived as Bugzilla considers it

NAME	keyworddefs
TYPE	TABLE
DESCRIPTION	Names and definitions of the keywords.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	SMALLINT		NO	PRI	A unique number identifying this keyword.
name	VARCHAR		NO	UNI	The keyword itself.
description	MEDIUMTEXT		YES		The meaning of the keyword.

NAME	keywords
TYPE	TABLE
DESCRIPTION	Bugs may have keywords. This table defines which bugs have which keywords. The keywords are defined in the keyworddefs table.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
bug_id	MEDIUMINT		NO	PRI	The bug (foreign key bugs.bug_id)
keywordid	SMALLINT		NO	PRI	The keyword ID (foreign key keyworddefs.id)

NAME	logincookies
TYPE	TABLE
DESCRIPTION	Bugzilla generates a cookie each time a user logs in, and uses it for subsequent authentication. The cookies generated are stored in this table.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
cookie	VARCHAR		NO	PRI	The cookie
userid	MEDIUMINT		NO	MUL	The user id; (foreign key profiles.userid)
ipaddr	VARCHAR		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
lastused	timestamp/DATETIME		NO	MUL	The timestamp of this login.
session	VARCHAR		NO		series of user login cookies

NAME	longdescs
TYPE	TABLE
DESCRIPTION	Each bug has a number of comments associated with it. These are stored individually in this table.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
comment_id	MEDIUMINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
bug_id	MEDIUMINT		NO	MUL	bug (foreign key bugs.bug_id)
who	MEDIUMINT		NO	MUL	the user who added this text (foreign key profiles.userid)
bug_when	DATETIME		NO	MUL	when the text was added
work_time	DECIMAL	/0.00	2)"/NO		Number of hours worked on this bug (for time tracking purposes).
thetext	MEDIUMTEXT		YES/NO	/MUL	the text itself.
isprivate	TINYINT		NO		Non-zero if this comment is private
already_wrapped	TINYINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
type	SMALLINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
extra_data	VARCHAR		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
public_in_it	TINYINT		YES		when a bug has an IssueTracker ID attached to it, Bugzilla will send any comments to each IssueTracker as well using XMLRPC so a person can check a box on BZ that says whether that comment should be public or private in the IssueTracker report and that value is also stored in the longdescs table

NAME	milestones
TYPE	TABLE
DESCRIPTION	Products may have milestones defined. The intention is that a milestone should be a point in a project at which a set of bugs has been resolved
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	MEDIUMINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
product_id	SMALLINT		NO	PRI/MUL	The product (foreign key products.id)
value	VARCHAR		NO		The name of the milestone (e.g. 3.1 RTM)
sortkey	SMALLINT		NO		A number used for sorting milestones for a given product.

NAME	namedqueries
TYPE	TABLE
DESCRIPTION	Users can name queries. Links to named query pages appear in a navigation footer bar on most Bugzilla pages. A query named (Default query) is a user default query
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	MEDIUMINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
userid	MEDIUMINT		NO	PRI/MUL	The user whose query this is (foreign key profiles.userid)
name	VARCHAR		NO		The name of the query.
query	MEDIUMTEXT		NO		The query (text to append to the query page URL).
query_type	TINYINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
public	TINYINT		NO		public is whether the query can be shared with others if others know the right query name
linkinfooter	tinyint(4)		NO		!! field in bugzilla_2.18 but not in bugzilla_3 !!

NAME	namedqueries_link_in_footer
TYPE	TABLE
DESCRIPTION	!! table found in bugzilla_3 but not in bugzilla_2_18 !!
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
namedquery_id	MEDIUMINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
user_id	MEDIUMINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	namedquery_group_map
TYPE	TABLE
DESCRIPTION	!! table found in bugzilla_3 but not in bugzilla_2_18 !!
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
namedquery_id	MEDIUMINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
group_id	MEDIUMINT		NO	MUL	!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	op_sys
TYPE	TABLE
DESCRIPTION	the possible values of the operating system field of a bug
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	tinyint(4)/SMALLINT		NO	PRI	a unique ID.
value	VARCHAR		NO	UNI	A possible value of the field
sortkey	SMALLINT		YES	MUL	!! field in bugzilla_3 and not in bugzilla_2.18 !!
isactive	TINYINT	1	YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	priority
TYPE	TABLE
DESCRIPTION	the possible values of the priority field of a bug
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	tinyint(4)/SMALLINT		NO	PRI	a unique ID.
value	VARCHAR		NO	UNI	A possible value of the field
sortkey	SMALLINT		YES	MUL	!! field in bugzilla_3 and not in bugzilla_2.18 !!
isactive	TINYINT	1	YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	products
TYPE	TABLE
DESCRIPTION	The work managed by Bugzilla is divided into products
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	SMALLINT		NO	PRI	The product ID.
name	VARCHAR		NO	UNI	The product name.
classification_id	SMALLINT	1	YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
description	MEDIUMTEXT		YES		The description of the product
milestoneurl	varchar(2000)/TINYTEXT		YES/NO		The URL of a document describing the product milestones.
disallownew	TINYINT		NO		New bugs can only be created for this product if this is 0.
votesperuser	SMALLINT		NO		Total votes which a single user has for bugs of this product.
maxvotesperbug	SMALLINT	10000	NO		Maximum number of votes which a bug may have.
votestoconfirm	SMALLINT		NO		How many votes are required for this bug to become NEW.
defaultmilestone	VARCHAR	---	NO		The default milestone for a new bug.
depends	TINYINT		YES		remnant of old interaction with another tool

NAME	profile_setting
TYPE	TABLE
DESCRIPTION	!! table found in bugzilla_3 but not in bugzilla_2_18 !!
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
user_id	MEDIUMINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
setting_name	VARCHAR		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
setting_value	VARCHAR		NO		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	profiles
TYPE	TABLE
DESCRIPTION	Bugzilla has users. Each user is represented by one row in the profiles table. Each user is referred by a number (profiles.userid) and an email address (profiles.login_name).
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
userid	MEDIUMINT		NO	PRI	user id
login_name	VARCHAR		NO	UNI	The user's email address. Used when logging in or providing mailto: links.
cryptpassword	VARCHAR		YES		The user's password. The Perl function crypt is used.
realname	VARCHAR		YES/NO		The user's real name.
disabledtext	MEDIUMTEXT		YES		If non-empty
disable_mail	TINYINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
mybugslink	TINYINT	1	NO		indicates whether a 'My Bugs' link should appear at the bottom of each page.
extern_id	VARCHAR		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
emailflags	MEDIUMTEXT		YES		a string that contains a user's email preferences for receiving bugzilla notifications
refreshed_when	DATETIME	"1900-01-01 00:00:00"/1900-01-01 00:00:00	NO		the date that a user's permissions were last derived, goes along with last_changed in groups table

NAME	profiles_activity
TYPE	TABLE
DESCRIPTION	This table is for recording changes to the profiles table. Currently it only records changes to group membership made with editusers.cgi. This allows the administrator to track group inflation. There is currently no code to inspect this table; only to add to it.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
userid	MEDIUMINT		NO	MUL	The profile which has changed (foreign key profiles.userid)
who	MEDIUMINT		NO	MUL	The user who changed it (foreign key profiles.userid)
profiles_when	DATETIME		NO	MUL	When it was changed
fieldid	MEDIUMINT		NO	MUL	The ID of the changed field (foreign key fielddefs.id)
oldvalue	VARCHAR		YES		The old value
newvalue	VARCHAR		YES		The new value.

NAME	quips
TYPE	TABLE
DESCRIPTION	Bugzilla supports quips: small text messages, often humorous, which appear along with search results. The quips are selected at random from a set
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
quipid	MEDIUMINT		NO	PRI	A unique ID.
userid	MEDIUMINT		NO		The user who added this quip (foreign key profiles.userid)
quip	text/MEDIUMTEXT		NO		The quip itself.
approved	TINYINT	1	NO		1 if this quip has been approved for display

NAME	rep_platform
TYPE	TABLE
DESCRIPTION	the possible values of the platform field of a bug
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	tinyint(4)/SMALLINT		NO	PRI	a unique ID.
value	VARCHAR		NO	UNI	A possible value of the field
sortkey	SMALLINT		YES	MUL	!! field in bugzilla_3 and not in bugzilla_2.18 !!
isactive	TINYINT	1	YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	resolution
TYPE	TABLE
DESCRIPTION	the possible values of the resolution field of a bug
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	tinyint(4)/SMALLINT		NO	PRI	a unique ID.
value	VARCHAR		NO	UNI	A possible value of the field
sortkey	SMALLINT		YES	MUL	!! field in bugzilla_3 and not in bugzilla_2.18 !!
isactive	TINYINT	1	YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	series
TYPE	TABLE
DESCRIPTION	Properties of the time-series datasets available (e.g. for plotting charts).
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
series_id	MEDIUMINT		NO	PRI	A unique ID.
creator	MEDIUMINT		NO/YES	MUL	The user who created this series (foreign key profiles.userid).NULL if this series is created by checksetup when first installing Bugzilla.
category	SMALLINT		NO	MUL	The series category. (foreign key series_categories.id)
subcategory	SMALLINT		NO	MUL	The series subcategory. (foreign key series_categories.id)
name	VARCHAR		NO		The series name.
frequency	SMALLINT		NO		The period between data samples for this series
last_viewed	DATETIME		YES		The time at which this dataset was last viewed.
query	MEDIUMTEXT		NO		a snippet of CGI which specifies a subset of bugs
is_public	TINYINT		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!
public	tinyint(1)	0	NO		!! field in bugzilla_2.18 but not in bugzilla_3 !!

NAME	series_categories
TYPE	TABLE
DESCRIPTION	categories of the time-series datasets available
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	SMALLINT		NO	PRI	A unique ID.
name	VARCHAR		NO	UNI	The category name.

NAME	series_data
TYPE	TABLE
DESCRIPTION	Data for plotting time-series charts.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
series_id	MEDIUMINT		NO	PRI	The series ID. (foreign key series.series_id)
series_date	DATETIME		NO	PRI	The time point at which this datum was collected.
series_value	MEDIUMINT		NO		The number of bugs in the dataset at this time point.

NAME	setting
TYPE	TABLE
DESCRIPTION	!! table found in bugzilla_3 but not in bugzilla_2_18 !!
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
name	VARCHAR		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
default_value	VARCHAR		NO		!! field in bugzilla_3 and not in bugzilla_2.18 !!
is_enabled	TINYINT	1	NO		!! field in bugzilla_3 and not in bugzilla_2.18 !!
subclass	VARCHAR		YES		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	setting_value
TYPE	TABLE
DESCRIPTION	!! table found in bugzilla_3 but not in bugzilla_2_18 !!
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
name	VARCHAR		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
value	VARCHAR		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
sortindex	SMALLINT		NO		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	status_workflow
TYPE	TABLE
DESCRIPTION	!! table found in bugzilla_3 but not in bugzilla_2_18 !!
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
old_status	SMALLINT		YES	MUL	!! field in bugzilla_3 and not in bugzilla_2.18 !!
new_status	SMALLINT		NO		!! field in bugzilla_3 and not in bugzilla_2.18 !!
require_comment	TINYINT		NO		!! field in bugzilla_3 and not in bugzilla_2.18 !!

NAME	tokens
TYPE	TABLE
DESCRIPTION	Tokens are sent to users to track activities such as creating new accounts and changing email addresses or passwords. They are also sent to browsers and used to track workflow, to prevent security problems (e.g. so that one can only delete groups from a session last seen on a group management page).
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
userid	MEDIUMINT		NO	MUL	The user to whom the token was issued. (foreign key profiles.userid)
issuedate	DATETIME		NO		The date at which the token was issued
token	VARCHAR		NO	PRI	The token itself.
tokentype	VARCHAR		NO		The type of the token. Possible values: 'account' when creating a new user account
eventdata	TINYTEXT		YES		The expected event

NAME	user_group_map
TYPE	TABLE
DESCRIPTION	This table records which users are members of each group, or can "bless" each group.
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
user_id	MEDIUMINT		NO	PRI	The user. (foreign key profiles.userid)
group_id	MEDIUMINT		NO	PRI	The group. (foreign key groups.id)
isbless	TINYINT		NO	PRI	0 if this row records group membership; 1 if this row records group bless privilege.
grant_type	TINYINT		NO	PRI	0 if this membership or privilege is explicit. 1 if it is derived from a group hierarchy (see the group_group_map table). 2 if it results from matching a regular expression (see groups.userregexp).

NAME	versions
TYPE	TABLE
DESCRIPTION	Product versions
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	MEDIUMINT		NO	PRI	!! field in bugzilla_3 and not in bugzilla_2.18 !!
value	VARCHAR		YES/NO		The name of the version
product_id	SMALLINT		NO	MUL	The product (foreign key products.id)

NAME	votes
TYPE	TABLE
DESCRIPTION	Users may vote for bugs which they think are important. A user can vote for a bug more than once
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
who	MEDIUMINT		NO	MUL	The user (foreign key profiles.userid)
bug_id	MEDIUMINT		NO	MUL	The bug (foreign key bugs.bug_id)
vote_count	SMALLINT		NO		How many votes.

NAME	watch
TYPE	TABLE
DESCRIPTION	Bugzilla lets users watch each other receiving each other Bugzilla email
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
watcher	MEDIUMINT		NO	PRI	The watching user (foreign key profiles.userid)
watched	MEDIUMINT		NO	PRI	The watched user (foreign key profiles.userid)

NAME	whine_events
TYPE	TABLE
DESCRIPTION	describes an email message: subject line and some body text to precede query results
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	MEDIUMINT		NO	PRI	The whine event ID
owner_userid	MEDIUMINT		NO	MUL	The user ID of the whine owner (foreign key profiles.userid). Must match namedqueries.userid for the queries associated with this event (whine_queries.query_name).
subject	VARCHAR		YES		The Subject of the whine emails.
body	TEXT		YES		Text to appear in the body of the whine emails before the bugs table.

NAME	whine_queries
TYPE	TABLE
DESCRIPTION	stores named queries, to which a title is given for use in email messages
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	MEDIUMINT		NO	PRI	A unique ID for this query.
eventid	MEDIUMINT		NO	MUL	The whine event ID (foreign key whine_events.id).
query_name	VARCHAR		NO		The query name (foreign key namedqueries.name).
sortkey	MEDIUMINT		NO		A key to order the queries for a given event ID.
onemailperbug	TINYINT		NO		1 if a separate email message should be sent for each bug matching the query;0 if a single email should be sent covering all the bugs.
title	VARCHAR		NO		The title displayed for this query in the message.

NAME	whine_schedules
TYPE	TABLE
DESCRIPTION	specifies the frequency with which an email should be sent to a particular user
FIELD	TYPE	DEFAULT	NUL	KEY	REMARK
id	MEDIUMINT		NO	PRI	a unique ID for this whine schedule.
eventid	MEDIUMINT		NO	MUL	The whine event ID (foreign key whine_events.id).
run_day	VARCHAR		YES		The day on which this whine should run. 'All' means every day. 'MF' means Monday to Friday inclusive. A three letter weekday abbreviation (e.g. Mon)
run_time	VARCHAR		YES		The time and date at which the whine should next be run. NULL if the whine has been changed and not rescheduled yet.
run_next	DATETIME		YES	/MUL	the date when the whine schedule will run next
mailto	MEDIUMINT		NO		Either a user ID (foreign key profiles.userid) or group ID (foreign key groups.id) identifying the user or users to whom to send whine messages.
mailto_type	tinyint(4)/SMALLINT		NO		0 if the mailto field is a user ID