encrypt is used to encrypt passwords.'),
('2.14', None, '%(VERSION_STRING)sThe Perl function crypt is used.')],
'realname': 'The user\'s real name.',
'groupset': 'The set of groups to which the user belongs. Each group corresponds to one bit and confers powers upon the user. See %(the-table-groups)s.',
'emailnotification': 'Controls when email reporting bug changes is sent to this user.',
'disabledtext': 'If non-empty, indicates that this account has been disabled and gives a reason. ',
'newemailtech': 'is non-zero if the user wants to user the "new" email notification technique.',
'mybugslink': 'indicates whether a "My Bugs" link should appear at the bottom of each page.',
'blessgroupset': 'Indicates the groups into which this user is able to introduce other users.',
'emailflags': 'Flags controlling when email messages are sent to this user.',
'refreshed_when': 'A timestamp showing when the derived group memberships in %(the-table-user_group_map)s were last updated for this user.',
'extern_id': 'The ID for environmental authentication (see the notes on authentication).',
'disable_mail': '1 to disable all mail to this user; 0 for mail to depend on the per-user email settings in %(table-email_setting)s.',
},
'profiles_activity': {
'userid': 'The profile which has changed (foreign key %(column-profiles-userid)s)',
'who': 'The user who changed it (foreign key %(column-profiles-userid)s)',
'profiles_when': 'When it was changed',
'fieldid': 'The ID of the changed field (foreign key %(column-fielddefs-id)s)',
'oldvalue': 'The old value',
'newvalue': 'The new value.',
},
'quips': {
'quipid': 'A unique ID.',
'userid': 'The user who added this quip (foreign key %(column-profiles-userid)s)',
'quip': 'The quip itself.',
'approved': '1 if this quip has been approved for display, 0 otherwise.',
},
'rep_platform': {
'value': 'A possible value of the field',
'isactive': '1 if this value is available in the user interface, 0 otherwise',
'sortkey': 'A number used to determine the order in which values are shown.',
'id': 'a unique ID.',
'visibility_value_id': 'If set, this value is only available if the chooser field (identified by %(column-fielddefs-value_field_id)s) has the value with this ID. Foreign key <field>.id, for example %(column-products-id)s or cf_<field>.id.',
},
'resolution': {
'value': 'A possible value of the field',
'isactive': '1 if this value is available in the user interface, 0 otherwise',
'sortkey': 'A number used to determine the order in which values are shown.',
'id': 'a unique ID.',
'visibility_value_id': 'If set, this value is only available if the chooser field (identified by %(column-fielddefs-value_field_id)s) has the value with this ID. Foreign key <field>.id, for example %(column-products-id)s or cf_<field>.id.',
},
'series': {
'series_id': 'A unique ID.',
'creator': ['The user who created this series (foreign key %(column-profiles-userid)s).',
(None, '2.23.2', '%(VERSION_STRING)s 0 if this series is created by checksetup when first installing Bugzilla.'),
('2.23.3', None, '%(VERSION_STRING)s NULL if this series is created by checksetup when first installing Bugzilla.'),],
'category': 'The series category. (foreign key %(column-series_categories-id)s)',
'subcategory': 'The series subcategory. (foreign key %(column-series_categories-id)s)',
'name': 'The series name.',
'frequency': 'The period between data samples for this series, in days.' ,
'last_viewed': 'The time at which this dataset was last viewed.',
'query': 'a snippet of CGI which specifies a subset of bugs, as for query.cgi',
'public': '1 if the series is visible to all users, 0 otherwise.',
},
'series_categories': {
'id': 'A unique ID.',
'name': 'The category name.',
},
'series_data': {
'series_id': 'The series ID. (foreign key %(column-series-series_id)s)',
'date': 'The time point at which this datum was collected.',
'value': 'The number of bugs in the dataset at this time point.',
'series_date': 'The time point at which this datum was collected.',
'series_value': 'The number of bugs in the dataset at this time point.',
},
'setting': {
'default_value': 'the value of this setting which will apply to any user who does not change it.',
'is_enabled': '1 if users are able to change this setting; 0 if it is automatic.',
'name': 'The name of the setting.',
'subclass': 'The name of the Perl subclass (of Setting) to which this setting applies.',
},
'setting_value': {
'sortindex': 'A number used to determine the order in which setting values are shown',
'name': 'The setting name. (foreign key %(column-setting-name)s)',
'value': 'The setting value',
},
'shadowlog': {
'id': 'unique id',
'ts': 'timestamp',
'reflected': '0',
'command': 'SQL command',
},
'status_workflow': {
'old_status': 'The old bug status, None for bug creation (foreign key %(column-bug_status-id)s)',
'new_status': 'The new bug status (foreign key %(column-bug_status-id)s)',
'require_comment': '1 if this transition requires a comment; 0 otherwise.',
},
'tokens': {
'userid': 'The user to whom the token was issued. (foreign key %(column-profiles-userid)s)',
'issuedate': 'The date at which the token was issued',
'token': 'The token itself.',
'tokentype': "The type of the token. Possible values: 'account' when creating a new user account, 'emailold' and 'emailnew' when changing email address, 'password' when changing a password, or 'session' for a session token.",
'eventdata': 'The expected event, for a session token.'
},
'ts_error': {
'error_time': 'The time at which the error occurred.',
'jobid': 'The job ID. Foreign key %(column-ts_job-jobid)s',
'message': 'The error message.',
'funcid': 'The function ID. Foreign key %(column-ts_funcmap-funcid)s.',
},
'ts_exitstatus': {
'jobid': 'The job ID. Foreign key %(column-ts_job-jobid)s',
'funcid': 'The function ID. Foreign key %(column-ts_funcmap-funcid)s.',
'status': 'The exit status. 0 for success.',
'completion_time': 'The time at which the job finished.',
'delete_after': 'A time after which this row can be deleted.',
},
'ts_funcmap': {
'funcid': 'A unique ID.',
'funcname': 'A unique function name, also known as an ability or a worker class name.',
},
'ts_job': {
'jobid': 'A unique ID.',
'funcid': 'The function ID. Foreign key %(column-ts_funcmap-funcid)s.',
'arg': 'State data for the job, stored as a frozen reference.',
'uniqkey': 'An arbitrary unique reference.',
'insert_time': 'not used.',
'run_after': 'A timestamp before which the job should not be run.',
'grabbed_until': 'Set while a worker is attempting this job; do not retry this job until this is in the past.',
'priority': 'Not used.',
'coalesce': 'A string used to indicate jobs which can be usefully pipelined by a single worker.',
},
'ts_note': {
'jobid': 'The job ID. Foreign key %(column-ts_job-jobid)s',
'notekey': 'Not used.',
'value': 'Not used.',
},
'user_group_map': {
'user_id': 'The user. (foreign key %(column-profiles-userid)s)',
'grant_type': '0 if this membership or privilege is explicit. 1 if it is derived from a group hierarchy (see %(the-table-group_group_map)s). 2 if it results from matching a regular expression (see %(column-groups-userregexp)s).' ,
'group_id': 'The group. (foreign key %(column-groups-id)s)',
'isbless': '0 if this row records group membership; 1 if this row records group "bless" privilege.',
'isderived': '0 if this membership or privilege is explicit. 1 if it is derived (e.g. from %(the-table-group_group_map)s or %(column-groups-userregexp)s).' ,
},
'user_series_map': {
'user_id': 'The user ID. (foreign key %(column-profiles-userid)s)',
'series_id': 'The series. (foreign key %(column-series-series_id)s)',
},
'versions': {
'id': 'A unique numeric ID',
'value': 'The name of the version',
'program': 'The product (foreign key %(column-products-product)s)',
'product_id': 'The product (foreign key %(column-products-id)s)',
},
'votes': {
'who': 'The user (foreign key %(column-profiles-userid)s)',
'bug_id': 'The bug (foreign key %(column-bugs-bug_id)s)',
'count': 'How many votes.',
},
'watch': {
'watcher': 'The watching user (foreign key %(column-profiles-userid)s)',
'watched': 'The watched user (foreign key %(column-profiles-userid)s)',
},
'whine_events': {
'id': 'The whine event ID, used to identify this event.',
'owner_userid': """The user ID of the whine owner (foreign key %(column-profiles-userid)s). Must match %(column-namedqueries-userid)s for the queries associated with this event (%(column-whine_queries-query_name)s).""",
'subject': 'The Subject of the whine emails.',
'body': 'Text to appear in the body of the whine emails before the bugs table.',
},
'whine_queries': {
'id': 'A unique ID for this query.',
'eventid': 'The whine event ID (foreign key %(column-whine_events-id)s).',
'query_name': 'The query name (foreign key %(column-namedqueries-name)s).',
'sortkey': 'A key to order the queries for a given event ID.',
'onemailperbug': """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': 'The title displayed for this query in the message.',
},
'whine_schedules': {
'id': """a unique ID for this whine schedule.""",
'eventid': 'The whine event ID (foreign key %(column-whine_events-id)s).',
'run_day': """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", "Thu") means only on that day.
An integer indicates a particular day of the month. 'last' means
the last day of the month.""",
'run_time': """The time at which this whine should run. An
integer indicates an hour of the day. An interval (e.g. "15min",
"30min") indicates that the whine should run repeatedly at that
interval.""",
'run_next': """The time and date at which the whine should next be
run. NULL if the whine has been changed and not rescheduled
yet.""",
'mailto_userid': """The ID of the user to whom to send whine
messages (foreign key %(column-profiles-userid)s).""",
'mailto': "Either a user ID (foreign key %(column-profiles-userid)s) or group ID (foreign key %(column-groups-id)s) identifying the user or users to whom to send whine messages.",
'mailto_type': "0 if the mailto field is a user ID, 1 if it is a group ID.",
},
}
# This is a map from table name to a map from column name to canonical
# column name. For use when a column has been renamed but not
# otherwise changed.
column_renamed = {
'votes': {
'vote_count': 'count',
},
'series': {
'is_public': 'public',
},
'series_data': {
'series_date': 'date',
'series_value': 'value',
},
'series_categories': {
'category_id': 'id',
},
'fielddefs': {
'fieldid': 'id',
},
}
# This is a map from table name to a map from column name to HTML
# remark for that column. At present, these remarks include schema
# change comments (which will eventually be generated automatically).
#
# Columns with no attached remarks are given 'None' as a placeholder,
# so we know to add a remark later.
column_added_remark = {
'attachments': {
'isobsolete': None,
'isprivate': None,
'isurl': None,
'modification_time': None,
},
'bug_severity': {
'visibility_value_id': None,
},
'bug_status': {
'is_open': None,
'visibility_value_id': None,
},
'bugs': {
'alias': None,
'deadline': None,
'keywords': None,
'everconfirmed': None,
'lastdiffed': None,
'product_id': 'replacing "product"',
'component_id': 'replacing "component"',
'reporter_accessible': None,
'assignee_accessible': None,
'qacontact_accessible': None,
'cclist_accessible': None,
'estimated_time': None,
'groupset': None,
'qa_contact': None,
'remaining_time': None,
'status_whiteboard': None,
'target_milestone': None,
'votes': None,
},
'bugs_activity': {
'attach_id': None,
'fieldid': 'replacing "field"',
'bug_when': 'replacing "when"',
'added': 'replacing "newvalue"',
'removed': 'replacing "oldvalue"',
},
'classifications': {
'sortkey': None,
},
'components': {
'description': None,
'name': 'replacing "value"',
'id': 'replacing "value" as the primary key',
'initialqacontact': None,
'product_id': 'replacing "program"',
},
'fielddefs': {
'obsolete': None,
'custom': None,
'type': None,
'enter_bug': None,
'buglist': None,
'value_field_id': None,
'visibility_field_id': None,
'visibility_value_id': None,
},
'flags': {
'is_active': None,
},
'flagtypes': {
'grant_group_id': None,
'request_group_id': None,
},
'group_group_map': {
'grant_type': 'replacing "isbless"',
},
'group_control_map': {
'editbugs': None,
'editcomponents': None,
'canconfirm': None,
},
'groups': {
'id': 'replacing "bit"',
'isactive': None,
'last_changed': None,
'icon_url': None,
},
'logincookies': {
'ipaddr': 'replacing hostname',
},
'longdescs': {
'type': None,
'extra_data': None,
'comment_id': None,
'already_wrapped': None,
'isprivate': None,
'work_time': None,
},
'milestones': {
'product_id': 'replacing "product"',
'id': None,
},
'namedqueries': {
'query_type': None,
'id': None,
},
'op_sys': {
'visibility_value_id': None,
},
'priority': {
'visibility_value_id': None,
},
'products': {
'classification_id': None,
'votestoconfirm': None,
'defaultmilestone': None,
'disallownew': None,
'maxvotesperbug': None,
'votesperuser': None,
'id': 'replacing "product" as the table key',
'name': 'replacing "product" as the product name',
},
'profiles': {
'blessgroupset': None,
'groupset': None,
'newemailtech': None,
'emailnotification': None,
'mybugslink': None,
'disabledtext': None,
'extern_id': None,
'emailflags': None,
'refreshed_when': None,
'disable_mail': None,
},
'quips': {
'approved': None,
},
'rep_platform': {
'visibility_value_id': None,
},
'resolution': {
'visibility_value_id': None,
},
'series': {
'public': None,
},
'setting': {
'subclass': None,
},
'user_group_map': {
'grant_type': 'replacing "isderived"',
},
'versions': {
'product_id': 'replacing "program"',
'id': None,
},
'whine_schedules': {
'mailto': None,
'mailto_type': None,
},
}
# This is a map from table name to a map from column name to HTML
# remark for that column. At present, these remarks include schema
# change comments (which will eventually be generated automatically).
#
# Columns with no attached remarks are given 'None' as a placeholder,
# so we know to add a remark later.
column_removed_remark = {
'attachments': {
'thedata': 'moved to %(the-table-attach_data)s',
},
'bugs': {
'area': None,
'long_desc': 'moved to %(the-table-longdescs)s',
'groupset': 'replaced by %(the-table-bug_group_map)s',
'product': 'replaced by "product_id"',
'component': 'replaced by "component_id"',
'assignee_accessible': None,
'qacontact_accessible': None,
},
'bugs_activity': {
'field': 'replaced by "fieldid"',
'oldvalue': 'replaced by "removed"',
'when': 'replaced by "bug_when"',
'newvalue': 'replaced by "added"',
},
'components': {
'value': 'replaced by "name" and "id"',
'program': 'replaced by "product_id"',
},
'fielddefs': {
'obsolete': None,
},
'flags': {
'is_active': None,
},
'groups': {
'bit': 'replaced by "id"',
'last_changed': 'redundant',
},
'group_group_map': {
'isbless': 'replaced by "grant_type"',
},
'logincookies': {
'cryptpassword': None,
'hostname': 'replaced by "ipaddr"',
},
'milestones': {
'product': 'replaced by "product_id"',
},
'namedqueries': {
'watchfordiffs': None,
'linkinfooter': 'replaced by %(the-table-namedqueries_link_in_footer)s.'
},
'products': {
'product': 'replaced with "id" and "name"',
},
'profiles': {
'password': None,
'emailflags': 'replaced by %(the-table-email_setting)s',
'groupset': 'replaced by %(the-table-user_group_map)s',
'emailnotification': 'replaced in part by %(column-profiles-emailflags)s',
'newemailtech': None,
'blessgroupset': 'replaced by %(the-table-user_group_map)s',
'refreshed_when': 'redundant',
},
'user_group_map': {
'isderived': 'replaced by "grant_type"',
},
'versions': {
'program': 'replaced by "product_id"',
},
'whine_schedules': {
'mailto_userid': None,
},
}
# This is a map from table name to a map from index name to HTML
# remark for that index. At present, these remarks include schema
# change comments (which will eventually be generated automatically).
#
# Indexes with no attached remarks are given 'None' as a placeholder,
# so we know to add a remark later.
index_remark = {
'attachments': {
'PRIMARY': None,
'bug_id': None,
'creation_ts': None,
'attachments_submitter_id_idx': None,
'attachments_modification_time_idx': None,
},
'attach_data': {
'PRIMARY': None,
},
'attachstatusdefs': {
'PRIMARY': None,
},
'attachstatuses': {
'PRIMARY': None,
},
'bug_group_map': {
'bug_id': None,
'group_id': None,
},
'bug_see_also': {
'bug_see_also_bug_id_idx': None,
},
'bug_severity': {
'PRIMARY': None,
'bug_severity_sortkey_idx': None,
'bug_severity_value_idx': None,
'bug_severity_visibility_value_id_idx': None,
},
'bug_status': {
'PRIMARY': None,
'bug_status_sortkey_idx': None,
'bug_status_value_idx': None,
'bug_status_visibility_value_id_idx': None,
},
'bugs': {
'PRIMARY': None,
'alias': None,
'area': None,
'assigned_to': None,
'creation_ts': None,
'delta_ts': None,
'bug_severity': None,
'bug_status': None,
'op_sys': None,
'priority': None,
'product': None,
'product_id': None,
'reporter': None,
'short_desc': None,
'version': None,
'component': None,
'component_id': None,
'resolution': None,
'target_milestone': None,
'qa_contact': None,
'votes': None,
},
'bugs_activity': {
'bug_id': None,
'when': None,
'bug_when': None,
'field': None,
'fieldid': None,
'bugs_activity_who_idx': None,
},
'bugs_fulltext': {
'PRIMARY': None,
'bugs_fulltext_short_desc_idx': None,
'bugs_fulltext_comments_idx': None,
'bugs_fulltext_comments_noprivate_idx': None,
},
'bz_schema': {
},
'category_group_map': {
'category_id': None,
},
'cc': {
'who': None,
'bug_id': None,
},
'classifications': {
'PRIMARY': None,
'name': None,
},
'components': {
'PRIMARY': None,
'product_id': None,
'name': None,
'bug_id': None,
'bug_when': None,
'fieldid': None,
},
'component_cc': {
'component_cc_user_id_idx': None,
},
'dependencies': {
'blocked': None,
'dependson': None,
},
'duplicates': {
'PRIMARY': None,
},
'email_setting': {
'email_setting_user_id_idx': None,
},
'fielddefs': {
'PRIMARY': None,
'name': None,
'sortkey': None,
'fielddefs_value_field_id_idx': None,
},
'flagexclusions': {
'type_id': None,
},
'flaginclusions': {
'type_id': None,
},
'flags': {
'PRIMARY': None,
'bug_id': None,
'setter_id': None,
'requestee_id': None,
'flags_type_id_idx': None,
},
'flagtypes': {
'PRIMARY': None,
},
'group_control_map': {
'product_id': None,
'group_id': None,
},
'group_group_map': {
'member_id': None,
},
'groups': {
'PRIMARY': None,
'bit': None,
'name': None,
},
'keyworddefs': {
'PRIMARY': None,
'name': None,
},
'keywords': {
'keywordid': None,
'bug_id': None,
},
'logincookies': {
'PRIMARY': None,
'lastused': None,
},
'longdescs': {
'PRIMARY': None,
'bug_id': None,
'who': None,
'bug_when': None,
'thetext': None,
},
'milestones': {
'PRIMARY': None,
'product': None,
'product_id': None,
},
'namedqueries': {
'PRIMARY': None,
'userid': None,
'watchfordiffs': None,
},
'namedqueries_link_in_footer': {
'namedqueries_link_in_footer_id_idx': None,
'namedqueries_link_in_footer_userid_idx': None,
},
'namedquery_group_map': {
'namedquery_group_map_group_id_idx': None,
'namedquery_group_map_namedquery_id_idx': None,
},
'op_sys': {
'PRIMARY': None,
'op_sys_sortkey_idx': None,
'op_sys_value_idx': None,
'op_sys_visibility_value_id_idx': None,
},
'priority': {
'PRIMARY': None,
'priority_sortkey_idx': None,
'priority_value_idx': None,
'priority_visibility_value_id_idx': None,
},
'products': {
'PRIMARY': None,
'name': None,
},
'profile_setting': {
'profile_setting_value_unique_idx': None,
},
'profiles': {
'PRIMARY': None,
'login_name': None,
'profiles_extern_id_idx': None,
},
'profiles_activity': {
'userid': None,
'profiles_when': None,
'fieldid': None,
},
'quips': {
'PRIMARY': None,
},
'rep_platform': {
'PRIMARY': None,
'rep_platform_sortkey_idx': None,
'rep_platform_value_idx': None,
'rep_platform_visibility_value_id_idx': None,
},
'resolution': {
'PRIMARY': None,
'resolution_sortkey_idx': None,
'resolution_value_idx': None,
'resolution_visibility_value_id_idx': None,
},
'series': {
'PRIMARY': None,
'creator': None,
'creator_2': None,
},
'series_categories': {
'PRIMARY': None,
'name': None,
},
'series_data': {
'series_id': None,
},
'setting': {
'PRIMARY': None,
},
'setting_value': {
'setting_value_ns_unique_idx': None,
'setting_value_nv_unique_idx': None,
},
'shadowlog': {
'PRIMARY': None,
'reflected': None,
},
'status_workflow': {
'status_workflow_idx': None,
},
'tokens': {
'PRIMARY': None,
'userid': None,
},
'ts_error': {
'ts_error_funcid_idx': None,
'ts_error_error_time_idx': None,
'ts_error_jobid_idx': None,
},
'ts_exitstatus': {
'PRIMARY': None,
'ts_exitstatus_funcid_idx': None,
'ts_exitstatus_delete_after_idx': None,
},
'ts_funcmap': {
'PRIMARY': None,
'ts_funcmap_funcname_idx': None,
},
'ts_job': {
'PRIMARY': None,
'ts_job_funcid_idx': None,
'ts_job_run_after_idx': None,
'ts_job_coalesce_idx': None,
},
'ts_note': {
'ts_note_jobid_idx': None,
},
'user_group_map': {
'user_id': None,
},
'user_series_map': {
'user_id': None,
'series_id': None,
},
'versions': {
'PRIMARY': None,
'versions_product_id_idx': None,
},
'votes': {
'who': None,
'bug_id': None,
},
'watch': {
'watched': None,
'watcher': None,
},
'whine_events': {
'PRIMARY': None,
},
'whine_queries': {
'PRIMARY': None,
'eventid': None,
},
'whine_schedules': {
'PRIMARY': None,
'run_next': None,
'eventid': None,
},
}
index_renamed = {
'attachments': {
'attachments_bug_id_idx': 'bug_id',
'attachments_creation_ts_idx': 'creation_ts',
},
'bug_group_map': {
'bug_group_map_bug_id_idx': 'bug_id',
'bug_group_map_group_id_idx': 'group_id',
},
'bugs': {
'bugs_votes_idx': 'votes',
'bugs_component_id_idx': 'component_id',
'bugs_product_id_idx': 'product_id',
'bugs_reporter_idx': 'reporter',
'bugs_bug_status_idx': 'bug_status',
'bugs_short_desc_idx': 'short_desc',
'bugs_bug_severity_idx': 'bug_severity',
'bugs_priority_idx': 'priority',
'bugs_alias_idx': 'alias',
'bugs_version_idx': 'version',
'bugs_target_milestone_idx': 'target_milestone',
'bugs_delta_ts_idx': 'delta_ts',
'bugs_assigned_to_idx': 'assigned_to',
'bugs_creation_ts_idx': 'creation_ts',
'bugs_resolution_idx': 'resolution',
'bugs_op_sys_idx': 'op_sys',
'bugs_qa_contact_idx': 'qa_contact',
},
'bugs_activity': {
'bugs_activity_bug_id_idx': 'bug_id',
'bugs_activity_bug_when_idx': 'bug_when',
'bugs_activity_fieldid_idx': 'fieldid',
},
'category_group_map': {
'category_group_map_category_id_idx': 'category_id',
},
'cc': {
'cc_bug_id_idx': 'bug_id',
'cc_who_idx': 'who',
},
'classifications': {
'classifications_name_idx': 'name',
},
'components': {
'components_name_idx': 'name',
'components_product_id_idx': 'product_id',
},
'dependencies': {
'dependencies_dependson_idx': 'dependson',
'dependencies_blocked_idx': 'blocked',
},
'fielddefs': {
'fielddefs_name_idx': 'name',
'fielddefs_sortkey_idx': 'sortkey',
},
'flagexclusions': {
'flagexclusions_type_id_idx': 'type_id',
},
'flaginclusions': {
'flaginclusions_type_id_idx': 'type_id',
},
'flags': {
'flags_bug_id_idx': 'bug_id',
'flags_setter_id_idx': 'setter_id',
'flags_requestee_id_idx': 'requestee_id',
},
'group_control_map': {
'group_control_map_group_id_idx': 'group_id',
'group_control_map_product_id_idx': 'product_id',
},
'group_group_map': {
'group_group_map_member_id_idx': 'member_id',
},
'groups': {
'groups_name_idx': 'name',
},
'keyworddefs': {
'keyworddefs_name_idx': 'name',
},
'keywords': {
'keywords_bug_id_idx': 'bug_id',
'keywords_keywordid_idx': 'keywordid',
},
'logincookies': {
'logincookies_lastused_idx': 'lastused',
},
'longdescs': {
'longdescs_bug_id_idx': 'bug_id',
'longdescs_bug_when_idx': 'bug_when',
'longdescs_thetext_idx': 'thetext',
'longdescs_who_idx': 'who',
},
'milestones': {
'milestones_product_id_idx': 'product_id',
},
'namedqueries': {
'namedqueries_userid_idx': 'userid',
},
'products': {
'products_name_idx': 'name',
},
'profiles': {
'profiles_login_name_idx': 'login_name',
},
'profiles_activity': {
'profiles_activity_profiles_when_idx': 'profiles_when',
'profiles_activity_userid_idx': 'userid',
'profiles_activity_fieldid_idx': 'fieldid',
},
'series': {
'series_creator_idx': 'creator_2',
},
'series_categories': {
'series_categories_name_idx': 'name',
},
'series_data': {
'series_data_series_id_idx': 'series_id',
},
'tokens': {
'tokens_userid_idx': 'userid',
},
'user_group_map': {
'user_group_map_user_id_idx': 'user_id',
},
'votes': {
'votes_bug_id_idx': 'bug_id',
'votes_who_idx': 'who',
},
'watch': {
'watch_watched_idx': 'watched',
'watch_watcher_idx': 'watcher',
},
'whine_queries': {
'whine_queries_eventid_idx': 'eventid',
},
'whine_schedules': {
'whine_schedules_eventid_idx': 'eventid',
'whine_schedules_run_next_idx': 'run_next',
},
}
index_removed_remark = {
'bugs': {
'area': None,
'short_desc': 'replaced by use of LIKE',
'product': 'replaced by "product_id"',
'component': 'replaced by "component_id"',
},
'bugs_activity': {
'when': 'replaced by "bug_when"',
'field': 'replaced by "fieldid"',
},
'groups': {
'bit': 'replaced by "PRIMARY"',
},
'longdescs': {
'thetext': 'replaced by %(the-table-bugs_fulltext)s',
},
'milestones': {
'product': 'replaced by "product_id"',
},
'namedqueries': {
'watchfordiffs': None,
},
'series': {
'creator': None,
},
}
index_added_remark = {
'bugs': {
'alias': None,
'component_id': 'replacing "component"',
'product_id': 'replacing "product"',
'qa_contact': None,
'target_milestone': None,
'op_sys': None,
'creation_ts': None,
'short_desc': None,
'votes': None,
},
'bug_severity': {
'bug_severity_visibility_value_id_idx': None,
},
'bug_status': {
'bug_status_visibility_value_id_idx': None,
},
'attachments': {
'attachments_submitter_id_idx': None,
'attachments_modification_time_idx': None,
},
'bugs_activity': {
'bug_when': 'replacing "when"',
'bugs_activity_who_idx': None,
'fieldid': 'replacing "field"',
'field': None,
},
'cc': {
'bug_id': None,
'who': None,
},
'components': {
'PRIMARY': None,
'name': None,
'product_id': None,
},
'fielddefs': {
'fielddefs_value_field_id_idx': None,
},
'flags': {
'flags_type_id_idx': None,
},
'groups': {
'PRIMARY': 'replacing "bit"',
},
'longdescs': {
'PRIMARY': None,
'who': None,
'thetext': None,
},
'milestones': {
'PRIMARY': None,
'product_id': 'replacing "product"',
},
'namedqueries': {
'PRIMARY': None,
},
'op_sys': {
'op_sys_visibility_value_id_idx': None,
},
'priority': {
'priority_visibility_value_id_idx': None,
},
'profiles': {
'profiles_extern_id_idx': None,
},
'rep_platform': {
'rep_platform_visibility_value_id_idx': None,
},
'resolution': {
'resolution_visibility_value_id_idx': None,
},
'products': {
'PRIMARY': None,
'name': None,
},
'versions': {
'PRIMARY': None,
'versions_product_id_idx': None,
},
}
notation_guide="""
Where the Bugzilla schema has been changed between %(FIRST_VERSION)s and %(LAST_VERSION)s, the change is noted in this document and marked out with color.
In the schema tables themselves, changed fields are noted and colored as follows:
| A field whose definition and use which has not changed between %(FIRST_VERSION)s and %(LAST_VERSION)s. |
| A field which was present in some previous Bugzilla release but which is absent from %(LAST_VERSION)s. |
| A field which is present in %(LAST_VERSION)s but was absent in some previous Bugzilla release. |
| A field whose definition has changed over time. |
Ravenbrook / Projects / Perforce Defect Tracking Integration / Version 2.2 Product Sources / Design
Perforce Defect Tracking Integration Project
This document is copyright © 2001-2003 Perforce Software, Inc. All rights reserved.
Redistribution and use of this document in any form, with or without modification, is permitted provided that redistributions of this document retain the above copyright notice, this condition and the following disclaimer.
This document is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the copyright holders and contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this document, even if advised of the possibility of such damage.
""", ] # This prelude is included in the generated schema doc prior to the # schema itself. prelude=["""Quick links to table definitions:
%(QUICK_TABLES_TABLE)sThis document describes the Bugzilla database schema for Bugzilla %(BUGZILLA_VERSIONS)s.
This document is generated automatically by a Python script which
constructs and colors the schema tables from the stored results of
MySQL queries. For more information about the scripts, see code.html.
The purpose of this document is to act as a reference for developers of Bugzilla and of code which interacts with Bugzilla (e.g. P4DTI).
The intended readership is P4DTI developers and Bugzilla developers and administrators.
This document is not confidential.
Please send any comments to <p4dti-comments@ravenbrook.com>, and problem reports to <p4dti-support@ravenbrook.com>.
Bugzilla is a defect tracking system, written in Perl with a CGI web GUI. By default it uses MySQL to store its tables.""", ('2.22', None, """%(VERSION_STRING)s PostgreSQL is also supported."""), """
%(NOTATION_GUIDE)sEach defect is called a bug and corresponds to one row in %(the-table-bugs)s. It is identified by its number, %(column-bugs-bug_id)s.
The work managed by Bugzilla is divided into products. The work for each product is in turn divided into the components of that product. Several properties of a new bug (e.g. ownership) are determined by the product and component to which it belongs. Each component is represented by a row in %(the-table-components)s.""", ('2.2', None, """ %(VERSION_STRING)sEach product is represented by a row in %(the-table-products)s."""), """
""", ("2.19.1", None, """%(VERSION_STRING)sProducts are grouped by "classification". This is optional and controlled by the parameter 'useclassification'. The classifications are used to help in finding bugs and in constructing meaningful time series, but have no other semantics in Bugzilla. There is a default classification, with ID 1, meaning "Unclassified".
"""), """Each bug has a status (%(column-bugs-bug_status)s). If a bug has a status which shows it has been resolved, it also has a resolution (%(column-bugs-resolution)s), otherwise the resolution field is empty.
""", ('3.1.1', None, """%(VERSION_STRING)sWorkflow is configurable. The possible status values are stored in %(the-table-bug_status)s; the transitions in %(the-table-status_workflow)s.
"""), """This table shows the possible values and valid transitions of the status field in the default workflow.
| Status | Resolved? | Description | Transitions | UNCONFIRMED | No | %(VERSION_STRING)sA new bug, when a product has voting | to NEW by voting or confirmation to ASSIGNED by acceptance to RESOLVED by resolution |
"""),
"""
|---|---|---|---|
| NEW | No | Recently added or confirmed | to ASSIGNED by acceptance to RESOLVED by analysis and maybe fixing to NEW by reassignment |
| ASSIGNED | No | Has been assigned | to NEW by reassignment to RESOLVED by analysis and maybe fixing |
| REOPENED | No | Was once resolved but has been reopened | to NEW by reassignment to ASSIGNED by acceptance to RESOLVED by analysis and maybe fixing |
| RESOLVED | Yes | Has been resolved (e.g. fixed, deemed unfixable, etc. See "resolution" column) | to REOPENED by reopening to VERIFIED by verification to CLOSED by closing |
| VERIFIED | Yes | The resolution has been approved by QA | to CLOSED when the product ships to REOPENED by reopening |
| CLOSED | Yes | Over and done with | to REOPENED by reopening |
This table shows the allowable values of the resolution field. The values "FIXED", "MOVED", and "DUPLICATE" have special meaning for Bugzilla. The other values may be changed, """, (None, '2.19.2', """%(VERSION_STRING)sby editing the schema of %(the-table-bugs)s, """), ('2.19.3', '2.23.2', """%(VERSION_STRING)sby manually updating %(the-table-resolution)s, """), ('2.23.3', None, """%(VERSION_STRING)sby using editvalues.cgi, """), """to add, remove, or rename values as necessary.
| Resolution | Meaning |
|---|---|
| FIXED | The bug has been fixed. |
| INVALID | The problem described is not a bug. |
| WONTFIX | This bug will never be fixed. |
| LATER | This bug will not be fixed in this version. |
| REMIND | This bug probably won't be fixed in this version. |
| DUPLICATE | This is a duplicate of an existing bug A description comment is added to this effect""", ('2.12', None, """, and %(VERSION_STRING)sa record is added to %(the-table-duplicates)s"""), """. |
| WORKSFORME | This bug could not be reproduced. | MOVED | %(VERSION_STRING)sThis bug has been moved to another database. | """), """
Bugzilla has users. Each user is represented by one row in %(the-table-profiles)s. Each user is referred by a number (%(column-profiles-userid)s) and an email address (%(column-profiles-login_name)s).
%(VERSION_STRING)sThere are various authentication mechanisms, including "environment variable authentication" (Bugzilla/Auth/Login/WWW/Env.pm) which uses environment variables to pass an external user ID (%(column-profiles-extern_id)s) to the Bugzilla CGI. The rest of this section describes the password-based authentication which has always been in Bugzilla and which is still widely used.
"""), """Each user has a password, used to authenticate that user to Bugzilla. The password is stored in %(column-profiles-cryptpassword)s in encrypted form.""", (None, '2.12', """ %(VERSION_STRING)s it is also stored in %(column-profiles-password)s as plaintext."""), """
On a successful login, Bugzilla generates a pair of cookies for the user's browser. On subsequent accesses, a user gets access if these cookie checks pass:
If the cookie checks fail, the user has to login (with their password), in which case a new row is added to %(the-table-logincookies)s and the user gets a new pair of cookies.
Rows in %(the-table-logincookies)s are deleted after 30 days (at user login time).
""", ('2.8', None, """%(VERSION_STRING)sUsers may vote for bugs which they think are important. A user can vote for a bug more than once. Votes are recorded in %(the-table-votes)s.
"""), ('2.10', None, """%(VERSION_STRING)sThe maximum number of votes per bug per user is product-dependent. Whether or not project managers pay any attention to votes is up to them, apart from the "confirmation by acclamation" process, which is as follows:New bugs have the status UNCONFIRMED. To enter the main workflow, they need the status NEW. To get the status NEW, they need a particular number of votes which is product-dependent.
"""), ('2.10', None, """%(VERSION_STRING)sProducts 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. An example might be a product release or a QA target. Milestones may be turned on and off with the parameter "usetargetmilestone".
If milestones are on, each bug has a "target milestone" (by which it should be fixed). A product may have a URL associated with it which locates a document describing the milestones for that product. This document itself is entirely outside Bugzilla. A product may also have a default target milestone, which is given to new bugs.
Milestones for a product have a "sort key", which allows them to be presented in a specific order in the user interface.
Milestones are kept in %(the-table-milestones)s.
"""), """Products may have versions. This allows more accurate bug reporting: "we saw it in 1.3.7b3".""", ('2.10', None, """Versions are totally independent of milestones."""), """
The operation of Bugzilla is controlled by parameters. These are set in editparams.cgi. The current values are stored in data/params. They are not stored in the database.
""", (None, '2.21.1', """%(VERSION_STRING)sThe set of parameters is defined in defparams.pl."""), ('2.22rc1',None,"""%(VERSION_STRING)sThe set of parameters is defined in the modules in Bugzilla/Config/."""), """
""", ('2.4', None, """%(VERSION_STRING)sBugzilla has "groups" of users. Membership of a group allows a user to perform certain tasks. Each group is represented by a row of %(the-table-groups)s.
There are a number of built-in groups, as follows:
| Name | Description |
|---|---|
| admin | %(VERSION_STRING)s Can administer all aspects of Bugzilla |
| tweakparams | Can tweak operating parameters |
| editgroupmembers | %(VERSION_STRING)sCan put people in and out of groups |
| editusers | Can edit or disable users |
| creategroups | Can create and destroy groups |
| editcomponents | Can create, destroy, and edit components and other controls (e.g. flagtypes). |
| editkeywords | %(VERSION_STRING)sCan create, destroy, and edit keywords |
| editbugs | %(VERSION_STRING)sCan edit all aspects of any bug |
| canconfirm | %(VERSION_STRING)sCan confirm a bug |
| editclassifications | %(VERSION_STRING)s Can edit classifications |
| bz_canusewhines | %(VERSION_STRING)s Can configure whine reports for self |
| bz_canusewhineatothers | %(VERSION_STRING)s Can configure whine reports for other users |
| bz_sudoers | %(VERSION_STRING)s Can impersonate another user |
| bz_sudo_protect | %(VERSION_STRING)s Cannot be impersonated |
New groups may be added and used to control access to sets of bugs. These "bug groups" have %(column-groups-isbuggroup)s set to 1. A bug may be in any number of bug groups. To see a bug, a user must be a member of all the bug groups which the bug is in.
"""), ('2.10', None, """%(VERSION_STRING)sIf the parameter "usebuggroups" is on, each product automatically has a bug group associated with it. If the parameter "usebuggroupsentry" is also on, a user must be in the product's bug group in order to create new bugs for the product.
"""), ('2.10', None, """%(VERSION_STRING)sUsers may be added to a group by any user who has the "bless" property for that group. The "bless" property itself may only be conferred by an administrator.
"""), ('2.4', None, """Group membership for new users and new groups is determined by matching %(column-groups-userregexp)s against the user's email address."""), ('2.10', None, """%(VERSION_STRING)sThe default configuration has universal regexps for the "editbugs" and "canconfirm" groups."""), ('2.4', None, """
"""), ('2.4', '2.16.7', """%(VERSION_STRING)sEach group corresponds to a bit in a 64-bit bitset, %(column-groups-bit)s. User membership in a group is conferred by the bit being set in %(column-profiles-groupset)s. Bug membership in a bug group is conferred by the bit being set in %(column-bugs-groupset)s."""), ('2.10', '2.16.7', """%(VERSION_STRING)sThe bless privilege for a group is conferred by the bit being set in %(column-profiles-blessgroupset)s."""), ('2.17.1', None, """%(VERSION_STRING)sUser membership in a group is conferred by a row in %(the-table-user_group_map)s, with %(column-user_group_map-isbless)s set to 0. The bless privilege for a group is conferred by a row with %(column-user_group_map-isbless)s set to 1. Bug membership in a bug group is conferred by a row in %(the-table-bug_group_map)s."""), ('2.4', None, """
"""), ('2.17.1', None, """%(VERSION_STRING)sGroups may be configured so that membership in one group automatically confers membership or the "bless" privilege for another group. This is controlled by %(the-table-group_group_map)s.
"""), ('2.19.1', None, """%(VERSION_STRING)sGroups may be configured so that the existence of a group is not visible to members of another group. This is controlled by %(the-table-group_group_map)s.
"""), ('2.17.3', None, """%(VERSION_STRING)sA product may be configured so that membership in one or more groups is required to perform certain actions on bugs in the product. Whether or not a new bug for the product is placed in a group is also configurable (note that user membership in a group is required to place an existing bug in that group). All this is controlled by %(the-table-group_control_map)s.
The %(column-group_control_map-membercontrol)s and %(column-group_control_map-othercontrol)s columns of that table determine the treatment of a given group for a new bug in a given product, depending on whether the bug is being created by a member or non-member of that group respectively. The possible values of these columns are as follows:
| value | name | meaning |
|---|---|---|
| 0 | NA | A bug for this product cannot be placed in this group. |
| 1 | Shown | A bug for this product may be placed in this group, but will not be by default. |
| 2 | Default | A bug for this product may be placed in this group, and is by default. |
| 3 | Mandatory | A bug for this product is always placed in this group. |
Only certain combinations of membercontrol/othercontrol are permitted, as follows:
| membercontrol | othercontrol | Notes |
|---|---|---|
| 0(NA) | 0(NA) | A bug for this product can never be placed in this group (so the option isn't presented). |
| 1 (Shown) | 0(NA) | Only members can place a bug in this group.This is the default setting. |
| 1 (Shown) | Anyone can place a new bug in this group. | |
| 2 (Default) | Anyone can place a bug in this group, and non-members will do so by default. | |
| 3 (Mandatory) | Anyone can place a bug in this group, and non-members will always do so. | |
| 2 (Default) | 0(NA) | Only members can place a bug in this group, and do so by default. |
| 2 (Default) | Anyone can place a bug in this group, and does so by default. | |
| 3 (Mandatory) | Members can place a bug in this group, and do so by default. Non-members always place a bug in this group. | |
| 3(Mandatory) | 3(Mandatory) | A bug for this product can never be removed from this group (so the option isn't presented). |
%(VERSION_STRING)sUsers can upload attachments to bugs. An attachments can be marked as a patch. Attachments are stored in %(the-table-attachments)s."""), ('2.16rc1', '2.16.7', """%(VERSION_STRING)sAttachments can be marked as "obsolete"."""), ('2.6', '2.20.7', """%(VERSION_STRING)sAttachment data is stored in %(column-attachments-thedata)s."""), ('2.21.1', None, """%(VERSION_STRING)sAttachment data is stored in %(the-table-attach_data)s."""), ('2.22rc1', None, """%(VERSION_STRING)sAttachments can be URLs, marked by the flag %(column-attachments-isurl)s. The URL itself is stored in %(column-attach_data-thedata)s."""), """
""", ('2.16rc1', '2.16.7', """%(VERSION_STRING)sEach attachment may have one of a number of "status" keywords associated with it. The status keywords are user-defined on a per-product basis. The set of status keywords is defined in %(the-table-attachstatusdefs)s. Whether a given attachment has a given status keyword is defined by %(the-table-attachstatuses)s.
"""), ('2.17.1', None, """%(VERSION_STRING)sAttachment statuses are implemented with the flags system.
"""), ('2.17.1', None, """%(VERSION_STRING)sBugs and attachments may be marked with "flags". The set of flag types is user-defined (using editflagtypes.cgi). For instance, a flag type might be "candidate for version 7.3 triage", or "7.3" for short. Flag types are recorded in %(the-table-flagtypes)s. Each flag type is either for bugs or for attachments, not both.
Actual flags are recorded in %(the-table-flags)s. Each flag has a status of "+" ("granted"), "-" ("denied") or "?" ("requested"). For instance, one bug might have flag "7.3+", and another might have flag "7.3-".
A status of "?" indicates that a user has requested that this item be given this flag. There is an special interface for viewing request flags (request.cgi). A request flag may be marked for the attention of a particular user, the "requestee".
A flag type may have a "CC list" of email addresses, of people to notify when a flag is requested.
By default, a single bug or attachment may receive several flags of the same type, with the same or different statuses and the same or different requestees. This may be disabled for any given flag type.
Particular flag types may only be available to bugs in certain products and components (or their attachments). This is recorded in %(the-table-flaginclusions)s. Particular flag types may not be available to bugs in certain products and components (or their attachments). This is recorded in %(the-table-flagexclusions)s.
Various features of flag types may be disabled: they can be made inactive, not requestable, not "requesteeable", not "multiplicable".
"""), ('2.10', None, """%(VERSION_STRING)sBugzilla users can define a number of keywords, and then give each bug a set of keywords. This is mainly for use in finding related bugs. The keywords are stored in %(the-table-keyworddefs)s, and the one-to-many mapping from bugs to keywords is stored in %(the-table-keywords)s, and also in %(column-bugs-keywords)s.
"""), ('2.6', None, """%(VERSION_STRING)sBugs may depend on other bugs being fixed. That is, it may be impossible to fix one bug until another one is fixed. Bugzilla records and displays such information and uses it to notify users when a bug changes (all contacts for all dependent bugs are notified when a bug changes).
Dependencies are recorded in %(the-table-dependencies)s.
"""), """Bugzilla keeps a record of changes made to bugs. This record is in %(the-table-bugs_activity)s. Each row in this table records a change to a field in %(the-table-bugs)s.""", ('2.10', None, """%(VERSION_STRING)sThe fields are referred to by a number which is looked up in %(the-table-fielddefs)s. This table records the name of the field and also a longer description used to display activity tables."""), """
Each bug has a "severity" field, %(column-bugs-bug_severity)s, indicating the severity of the impact of the bug. There is no code in Bugzilla which distinguishes the values of this field, although it may naturally be used in queries.""", ('2.19.3', None, """%(VERSION_STRING)sThe set of values available for this field is stored in %(table-bug_severity)s and can be controlled by the administrator. """), """The intended meanings of the built-in values of this field are as follows:
| Value | Intended meaning |
|---|---|
| Blocker | Blocks development and/or testing work |
| Critical | Crashes, loss of data, severe memory leak |
| Major | Major loss of function |
| Minor | Minor loss of function, or other problem where easy workaround is present |
| Trivial | Cosmetic problem |
| Enhancement | Request for enhancement |
When a bug changes, email notification is sent out to a number of users:
""", ('2.12', None , """%(VERSION_STRING)sIndividual users may filter these messages according to the way in which the bug changes and their relationship to the bug. """), ('2.12', '2.19.2' , """%(VERSION_STRING)sThese filtering preferences are recorded in %(column-profiles-emailflags)s. """), ('2.19.3', None , """%(VERSION_STRING)sThese filtering preferences are recorded in the %(table-email_setting)s table. """), ('2.12', None, """
"""), (None, '2.17.3', """%(VERSION_STRING)sThis is handled by the "processmail" script. """), ('2.17.4', None, """%(VERSION_STRING)sThis is handled by the Bugzilla::Bugmail module, which is invoked by the template system (from Bugzilla::Template) when it encounters a call to SendBugMail() in a template. """), ('3.3.1', None, """
%(VERSION_STRING)sIf the parameter "use_mailer_queue" is set, all email is queued to be sent asynchronously. This is managed by a third-party general-purpose Perl job queueing system called TheSchwartz, using several database tables of its own (%(table-ts_error)s, %(table-ts_exitstatus)s, %(table-ts_funcmap)s, %(table-ts_job)s, and %(table-ts_note)s)."""), """Each bug has a number of comments associated with it. """, (None, '2.8', """%(VERSION_STRING)sThese are stored concatenated in %(column-bugs-long_desc)s"""), ('2.10', None, """%(VERSION_STRING)sThese are stored individually in %(the-table-longdescs)s."""), """
They are displayed as the "Description" on the bug form, ordered by date and annotated with the user and date. Users can add new comments with the "Additional comment" field on the bug form.
""", ('2.10', None, """%(VERSION_STRING)sUsers 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's default query. Named queries are stored in %(the-table-namedqueries)s.
"""), ('2.23.3', None, """%(VERSION_STRING)sIf the parameter "querysharegroup" is set, it names a group of users who are empowered to share named queries. An empowered user can share a given named query they create with all the members of a group, as long as he or she has the "bless" property for that group. A query can only be shared with a single group. Sharing is recorded in %(the-table-namedquery_group_map)s.
%(VERSION_STRING)sAny user able to use a given named query can control whether or not that query appears in his or her navigation footer bar. This is recorded in %(the-table-namedqueries_link_in_footer)s.
"""), ('2.17.5', None, """%(VERSION_STRING)sBugzilla can draw general time-series charts. There are a number of default time series. Each product has a default series for each bug status or resolution (for instance "how many bugs are INVALID in product Foo") and each component has a default series for all open bugs (UNCONFIRMED/NEW/ASSIGNED/REOPENED) and one for all closed bugs (RESOLVED/VERIFIED/CLOSED). A user can also define a new time series based on any query, and give it a "frequency" (actually a period, measured in days). The set of series is stored in %(the-table-series)s.
To collect the data for the time series, the Bugzilla administrator needs to arrange for the collectstats.pl script to be run every day. This script stores the data in %(the-table-series_data)s.
Series have categories and subcategories, which are provided in order to make it easier to manage large numbers of series. They are normalized in %(the-table-series_categories)s.
"""), ('2.17.5', None, """By default, a time series is "private": only visible to the user who created it. An administrator may make a time series "public", or visible to other users."""), ('2.17.5', '2.18rc2', """%(VERSION_STRING)s this is determined by the "subscription" system (see below)."""), ('2.18rc3', None, """%(VERSION_STRING)sthis is determined by %(column-series-public)s."""), ('2.17.5', None, """
"""), ('2.17.5', '2.18rc2', """%(VERSION_STRING)sIf a series is "private" (not "public") then users may "subscribe" to it. Each user is automatically subscribed to any series created by that user. The subscription is recorded in %(the-table-user_series_map)s. If all users unsubscribe from a time series, data will stop being collected on it (by setting the period to 0 days). A series is "public" if %(column-user_series_map-user_id)s is zero.
"""), ('2.18rc3', None, """%(VERSION_STRING)sVisibility of a time series to a user is determined on a per-category basis using the groups system. The group memberships required to see a time series in a given category are recorded in %(the-table-category_group_map)s. A user may see a time series if they are in all the groups for the category and either ths user created the series or it is public.
"""), ('2.10', None, """%(VERSION_STRING)sBugzilla lets users "watch" each other; receiving each other's Bugzilla email. For instance, if Sam goes on holiday, Phil can "watch" her, receiving all her Bugzilla email. This is set up by the user preferences (userprefs.cgi), recorded in %(the-table-watch)s and handled by the email subsystem.
"""), ('2.10', '2.17.2', """%(VERSION_STRING)s: Bugzilla can maintain a shadow, read-only copy of everything in another database (with the parameter "shadowdb"). If the parameter "queryagainstshadowdb" is on, queries were run against the shadow. A record of SQL activity since the last reflection is kept in %(the-table-shadowlog)s.
"""), ('2.17.1', None, """%(VERSION_STRING)s Bugzilla can track time for each bug, if the "timetrackinggroup" parameter is set. Members of that group get the ability to estimate the amount of effort (measured in hours) a bug will take to fix, either when creating or when editing the bug. Members of that group are also permitted to record hours of effort spent on the bug
%(column-longdescs-work_time)s records each increment of work. The sum of this column for a bug is computed to display as "Hours Worked" for the bug.
%(column-bugs-estimated_time)s is the estimate for how much time the bug will take in total, displayed as "Orig. Est.". This can be changed by members of the timetrackinggroup.
%(column-bugs-remaining_time)s is the current estimate for how much more time the bug will take to fix, displayed as "Hours Left". This can be changed by members of the timetrackinggroup.
The total of "Hours Left" and "Hours Worked" is shown as "Current Est.": the current estimate of the total effort required to fix the bug. "Hours Worked" as a percentage of "Current Est" is shown as "%% Complete". "Current Est" deducted from "Orig. Est" is shown as "Gain"
"""), ('2.19.3', None, """%(VERSION_STRING)s%(column-bugs-deadline)s records a calendar deadline for the bug.
"""), """Bugzilla has a system for sending "whine" email messages to specified users on a regular basis. This system relies on the administrator configuring the Bugzilla server to run a script at regular intervals (e.g. by using crontab).
The whineatnews.pl script should be run once a day.
For each bug which has status NEW or REOPENED, and which has not
changed for a certain number of days, it sends a message to the bug's
owner. The number of days is controlled by a Bugzilla parameter
called "whinedays". The content of the email message is controlled by
a Bugzilla parameter called "whinemail".
%(VERSION_STRING)sThe whine.pl
script runs a separate whine system, which allows a number of whine
schedules to be established with varying frequency (up to every 15
minutes), criteria, and content of whine messages. It is configured
with editwhines.cgi. Obviously, whine.pl
needs to be run every 15 minutes in order to send the most frequent
messages.
Users must be in the bz_canusewhines group to configure whine messages. Users must be in the bz_canusewhineatothers group to configure whine messages to be sent to other users. These restrictions are checked when configuring whine messages and also before messages are sent, so removing a user from one of these groups will disable any whines which that user has configured.
A whine schedule, stored in %(the-table-whine_schedules)s, specifies the frequency with which an email should be sent to a particular user. The email is specified with a whine event (see below). There is a variety of ways of specifying the frequency: both days (every day, a particular day of the week, weekdays only, a particular day of the month, the last day of the month) and times (a particular hour, or every 15, 30, or 60 minutes).
"""), ('2.19.3', None, """%(VERSION_STRING)sWhines may be scheduled for groups as well as users.
"""), ('2.19.1', None, """A whine schedule, stored in %(the-table-whine_schedules)s, specifies the frequency with which an email should be sent to a particular user. The email is specified with a whine event (see below). There is a variety of ways of specifying the frequency: both days (every day, a particular day of the week, weekdays only, a particular day of the month, the last day of the month) and times (a particular hour, or every 15, 30, or 60 minutes).
A whine event, stored in %(the-table-whine_events)s, describes an email message: subject line and some body text to precede query results. A message may consist of more than one whine query.
A whine query, stored in %(the-table-whine_queries)s is a named query, to which a title is given for use in email messages. Whine queries are stored in %(the-table-whine_queries)s. A whine query may specify that a separate message is to be sent for each bug found.
"""), ('2.19.3', None, """%(VERSION_STRING)sThere are several user-interface preferences, each of which can take a number of values. Each preference has a row in the %(table-setting)s table, and possible values in the %(table-setting_value)s table. The administrator may set a default value for each preference (%(column-setting-default_value)s) and determine whether users are able to override the default (%(column-setting-is_enabled)s). The user's individual preferences are recorded in the %(table-profile_setting)s table.
"""), """Bugzilla supports "quips": small text messages, often humorous, which appear along with search results. The quips are selected at random from a set.
""", (None, '2.16.7', """%(VERSION_STRING)sThe quips are stored in a file called "data/comments"."""), ('2.17.1', None, """ %(VERSION_STRING)sThe quips are stored in %(the-table-quips)s.
"""), ('2.14', None, """%(VERSION_STRING)sQuips may be entered or deleted
using quips.cgi.
%(VERSION_STRING)sQuips may be entered by any user but must be approved by an administrator before they can be displayed.
"""), ('3.3.2', None, """%(VERSION_STRING)sBugzilla can record connections to bugs in other instances of Bugzilla, if the parameter "use_see_also" is set. The connections are displayed as clickable URLs and are stored as URLs in %(the-table-bug_see_also)s. They are validated according to the system's notion of a valid form for Bugzilla URLs.
"""), ('2.23.1', None, """%(VERSION_STRING)sBugzilla supports custom fields. Each custom
field is a new column in %(the-table-bugs)s, with a name beginning
cf_. The presence of each custom field is indicated by a
row in %(the-table-fielddefs)s, with %(column-fielddefs-custom)s set
to 1. The type of each custom field is specified by
%(column-fielddefs-type)s:
The value 1 (FIELD_TYPE_FREETEXT) indicates a free-form text field (type varchar(255)).
"""), ('2.23.3', None, """%(VERSION_STRING)sThe value 2 (FIELD_TYPE_SINGLE_SELECT) indicates
a single-select field (type varchar(64), not null, default '---').
The allowable values of that field are stored in a special table with
the same cf_<name> name as the field, and a schema
like this:
| Field | Type | Default | Properties | Remarks |
|---|---|---|---|---|
| id | smallint | 0 | auto_increment | a unique ID. |
| value | varchar(64) | '' | - | the text value |
| sortkey | smallint | 0 | - | a number determining the order in which values appear. |
| isactive | tinyint | 1 | - | 1 if this value is currently available, 0 otherwise |
| visibility_value_id | smallint | 0 | - | If set, this value is only available if the chooser field (identified by %(column-fielddefs-value_field_id)s) has the value with this ID. Foreign key <field>.id, for example %(column-products-id)s or cf_<field>.id. |
Indexes:
| Name | Fields | Properties | Remarks |
|---|---|---|---|
| PRIMARY | id | unique | - |
| cf_<field>_value_idx | value | unique | - |
| cf_<field>_sortkey_idx | sortkey | - | - |
| cf_<field>_visibility_value_id_idx | visibility_value_id | - | - |
%(VERSION_STRING)sThe value 3 (FIELD_TYPE_MULTI_SELECT)
indicates a multi-select field. The allowable values of that field
are stored in a cf_<name> table as for
FIELD_TYPE_SINGLE_SELECT, above. The actual values of the field are
not stored in %(the-table-bugs)s, unlike other custom fields, Instead
they are stored in another table, with the name
bug_cf_<name>, and a schema like this:
| Field | Type | Default | Properties | Remarks |
|---|---|---|---|---|
| bug_id | mediumint | 0 | The bug ID (foreign key %(column-bugs-bug_id)s). | |
| value | varchar(64) | '' | - | the value (foreign key cf_<name>.value). |
Indexes:
| Name | Fields | Properties | Remarks |
|---|---|---|---|
| cf_<field>_bug_id_idx | bug_id, value | unique | - |
%(VERSION_STRING)sThe value 4 (FIELD_TYPE_TEXTAREA) indicates a large text-box field (type mediumtext).
"""), ('3.1.3', None, """%(VERSION_STRING)sThe value 5 (FIELD_TYPE_DATETIME) indicates a date/time field (type datetime).
"""), ('3.3.1', None, """%(VERSION_STRING)sThe value 6 (FIELD_TYPE_BUG_ID) indicates a bug ID field (type mediumint).
"""), ('2.23.1', '2.23.2', """%(VERSION_STRING)sCustom fields are
manipulated from the command-line with the customfield.pl
script.
%(VERSION_STRING)sCustom fields are configured
using editfield.cgi.
This table gives the dates of all the Bugzilla releases since 2.0.
| Date | Release | Notes |
|---|
In Bugzilla release 2.2, the following schema changes were made:
In Bugzilla release 2.4, the following schema changes were made:
In Bugzilla release 2.6, the following schema changes were made:
In Bugzilla release 2.8, the following schema changes were made:
In Bugzilla release 2.10, the following schema changes were made:
In Bugzilla release 2.12, the following schema changes were made:
In Bugzilla release 2.14, the following schema changes were made:
The schema is identical in Bugzilla releases 2.14 and 2.14.1.
"""), ('2.14.2', '2.14.2', """In Bugzilla release 2.14.2, the following schema change was made:
The schema is identical in Bugzilla releases 2.14.2, 2.14.3, 2.14.4, and 2.14.5.
"""), ('2.16rc1', '2.16', """In Bugzilla release 2.16 (and the release candidates 2.16rc1 and 2.16rc2), the following schema changes were made:
The schema is identical in Bugzilla releases 2.16rc1, 2.16rc2, 2.16, 2.16.1, 2.16.2, 2.16.3, 2.16.4, 2.16.5, 2.16.6, 2.16.7, 2.16.8, 2.16.9, 2.16.10, and 2.16.11.
"""), ('2.17.1', '2.17.1', """In Bugzilla release 2.17.1, the following schema changes were made:
The groups system was radically changed. This included the following detailed schema changes:
The schema is identical in Bugzilla releases 2.17.1 and 2.17.2.
"""), ('2.17.3', '2.17.3', """In Bugzilla release 2.17.3, the following schema changes were made:
In Bugzilla release 2.17.4, the following schema changes were made:
In Bugzilla release 2.17.5, the following schema changes were made:
The schema is identical in Bugzilla releases 2.17.5 and 2.17.6.
"""), ('2.17.7', '2.17.7', """In Bugzilla 2.17.7, the following schema changes were made:
In Bugzilla 2.18rc1, the following schema changes were made:
The schema is identical in Bugzilla releases 2.18rc1 and 2.18rc2.
"""), ('2.18rc3', '2.18rc3', """In Bugzilla 2.18rc3, the following schema changes were made:
The schema is identical in Bugzilla releases 2.18rc3 and 2.18.
"""), ('2.18.1', '2.18.1', """In Bugzilla 2.18.1, the following schema changes were made:
In Bugzilla 2.18.2, the following schema changes were made:
The schema is identical in Bugzilla releases 2.18.2, 2.18.3, 2.18.4, 2.18.5, and 2.18.6.
"""), ('2.19.1', '2.19.1', """In Bugzilla 2.19.1, the following schema changes were made:
In Bugzilla 2.19.2, the following schema changes were made:
In Bugzilla 2.19.3, the following schema changes were made:
In Bugzilla 2.20rc1, the following schema changes were made:
In Bugzilla 2.20rc2, the following schema changes were made:
The schema is identical in Bugzilla releases 2.20rc2, 2.20, 2.20.1, 2.20.2, 2.20.3, 2.20.4, 2.20.5, 2.20.6, and 2.20.7.
"""), ('2.21.1', '2.21.1', """In Bugzilla 2.21.1, the following schema changes were made:
In Bugzilla 2.22rc1, the following schema changes were made:
The schema is identical in Bugzilla releases 2.22rc1, 2.22, 2.22.1, 2.22.2, 2.22.3, 2.22.4, 2.22.5, 2.22.6, and 2.22.7.
"""), ('2.23.1', '2.23.1', """In Bugzilla 2.23.1, the following schema changes were made:
cf_<name> in %(the-table-bugs)s.In Bugzilla 2.23.2, the following schema change was made:
In Bugzilla 2.23.3, the following schema changes were made:
cf_<name>.In Bugzilla 2.23.4, the following schema changes were made:
The schema is identical in Bugzilla releases 2.23.4, 3.0rc1, 3.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.0.6, 3.0.7, 3.0.8, and 3.0.9.
"""), ('3.1.1', '3.1.1', """In Bugzilla 3.1.1, the following schema changes were made:
In Bugzilla 3.1.2, the following schema change was made:
In Bugzilla 3.1.3, the following schema changes were made:
In Bugzilla 3.1.4, the following schema change was made:
The schema is identical in Bugzilla releases 3.1.4, 3.2rc1, 3.2rc2, 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, and 3.2.5.
"""), ('3.3.1', '3.3.1', """In Bugzilla 3.3.1, the following schema changes were made:
In Bugzilla 3.3.2, the following schema changes were made:
The schema is identical in Bugzilla releases 3.3.2 and 3.3.3.
"""), ('3.3.4', '3.3.4', """In Bugzilla 3.3.4, the following schema changes were made:
The schema is identical in Bugzilla releases 3.3.4, 3.4rc1, 3.4, 3.4.1, and 3.4.2.
"""), """To select bug number n:
select * from bugs where bug_id = n
To get a complete list of user ids and email addresses:
select userid, login_name from profiles
To get the email address of user n:
select login_name from profiles where userid = n
To get the set of cc addresses of bug n:
select login_name from cc, profiles
where cc.bug_id = n
and profiles.userid = cc.who
%(VERSION_STRING)sTo select the long descriptions of bug n, together with the name and email address of the commenters:
select profiles.login_name, profiles.realname,
longdescs.bug_when, longdescs.thetext
from longdescs, profiles
where profiles.userid = longdescs.who
and longdescs.bug_id = n
order by longdescs.bug_when
To find out the groups of user n:
"""), ('2.4', '2.16.7', """%(VERSION_STRING)s
select groupset from profiles where userid = n
%(VERSION_STRING)s
select group_id from user_group_map where userid = n and isbless=0
| 2000-11-14 | NB | Created. |
| 2001-03-02 | RB | Transferred copyright to Perforce under their license. |
| 2001-04-06 | NB | Added sample queries. |
| 2001-09-12 | NB | Updated to reflect schema updates in Bugzilla 2.12 and 2.14 |
| 2002-01-31 | NB | Added notes on Bugzilla 2.14.1. |
| 2002-05-31 | NB | Updated for Bugzilla 2.16 (based on 2.16rc1). |
| 2002-09-26 | NB | Updated for Bugzilla 2.16/2.14.2/2.14.3. |
| 2002-10-04 | NB | Added notes on Bugzilla 2.14.4 and 2.16.1, and on identical schemas. |
| 2003-05-14 | NB | Added extensive notes on schema changes, in section 2. |
| 2003-06-06 | NB | Added table of Bugzilla releases showing release date and support status. |
| 2003-06-06 | NB | Added notes on schema changes in 2.17.x. |
| 2003-06-13 | NB | Added first cut at description of new Bugzilla tables. |
| 2003-06-27 | NB | Added more on recent schema changes. Colour-coded all schema changes. |
| 2003-07-09 | NB | Completely changed the way this document is produced. The schema tables themselves are now created and coloured automatically by querying MySQL. |
| 2003-11-04 | NB | Add Bugzilla 2.16.4 and 2.17.5. |
| 2003-11-10 | NB | Add Bugzilla 2.17.6. |
| 2004-03-19 | NB | Add Bugzilla 2.17.7; improve documentation of the groups system; improve automated schema change descriptions. |
| 2004-03-26 | NB | Add documentation of the flags system, the time series system, and the time tracking system. |
| 2004-04-30 | NB | Correct some documentation of the time series system based on feedback from the author. |
| 2004-07-14 | NB | Add 2.16.6 and 2.18rc1. |
| 2004-07-28 | NB | Add 2.18rc2. |
| 2004-11-11 | NB | Add 2.16.7, 2.18rc3, 2.19.1. Change document-generation code to improve colouring, link consistency, control, and robustness. |
| 2004-11-12 | NB | Turn into CGI, using schemas stored in Python pickles. |
| 2004-11-13 | NB | Add 2.0, 2.2, 2.4, 2.6. 2.8, for completeness. |
| 2004-12-03 | NB | Add notes on quips and a few missing foreign key links. |
| 2005-01-18 | NB | Add 2.16.8, 2.18, and 2.19.2. |
| 2005-05-19 | NB | Add 2.16.9, 2.16.10, 2.18.1, and (preliminarily) 2.19.3. |
| 2005-09-15 | NB | Add 2.18.2, 2.18.3, 2.20rc1, 2.20rc2, and complete remarks for 2.19.3. |
| 2005-10-03 | NB | Add 2.18.4, 2.20, 2.21.1 |
| 2006-05-18 | NB | Add 2.16.11, 2.18.5, 2.20.1, 2.22rc1, 2.20.2, 2.22, 2.23.1. |
| 2006-10-31 | NB | Add recent releases, to 2.18.6, 2.20.3, 2.22.1, 2.23.3. |
| 2007-05-11 | NB | Add recent releases 2.20.4, 2.22.2, 2.23.4, 3.0rc1, 3.0. |
| 2008-02-29 | NB | Add recent releases 3.0.1, 3.0.2, 3.0.3, 3.1.1, 3.1.2, 3.1.3. |
| 2009-07-31 | NB | Add recent releases 2.20.7, 2.22.5, 2.22.6, 2.22.7, 3.0.5, 3.0.6, 3.0.7, 3.0.8, 3.2rc1, 3.2rc2, 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.4rc1, and 3.4. |
Generated at %(TIME)s
by %(SCRIPT_ID)s
from %(REMARKS_ID)s