| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
clipboard, as well as by drag-and-dropping a file from desktop
|
|
of bug ID
|
|
|
|
|
|
to /rest/user and /rest/user/suggest responses
|
|
|
|
|
|
disallow duplicate nicks
|
|
|
|
contain U+FFFF
|
|
row format, and changes charset to utf8mb4)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
standard options; mark PDF viewable
|
|
or /bug/ALIAS."
This reverts commit 404dc5496967203c5f99755340f43d712420446a.
|
|
|
|
class method DYNAMIC_COLUMNS
When working on bug 1253535 I kept encountering the fragility of our model system.
This fragility involves two things:
1) Extensions adding new columns to model objects
2) The use of those model objects in checksetup.
In particular, the SecureMail extension causes this problem because (at checksetup-time) we need to lookup certain Group objects.
Thus I propose to
1) allow model classes to take their list of columns from the informations schema (exposed via `bz_table_columns_real`)
2) Have Bugzilla::Group do this when being used in a commandline (e.g. checksetup) context.
|
|
|
|
|
|
|
|
|
|
|
|
/bug/ALIAS.
|
|
|
|
|
|
$self->type()
|
|
|
|
|
|
|
|
|
|
more compile errors in tests
|
|
|
|
|
|
|
|
|
|
files for its filters
|
|
|
|
|
|
bugmail and disabledtext fields of a user
|
|
|
|
|
|
all other logs as info
|
