Closed
Bug 287331
Opened 20 years ago
Closed 16 years ago
Move bz_get_field_defs from Bugzilla::DB to Bugzilla::Field
Categories
(Bugzilla :: Bugzilla-General, enhancement)
Tracking
()
RESOLVED
INVALID
People
(Reporter: mkanat, Assigned: mkanat)
Details
I think that this would be an easy way to start working on Bugzilla::Field. This function really doesn't belong in Bugzilla::DB anyhow, it just kinda got moved there with the other checksetup functions.
| Assignee | ||
Updated•20 years ago
|
Severity: normal → enhancement
Target Milestone: --- → Bugzilla 2.22
| Assignee | ||
Updated•19 years ago
|
Assignee: general → mkanat
Target Milestone: --- → Bugzilla 2.24
| Assignee | ||
Updated•18 years ago
|
Target Milestone: Bugzilla 3.0 → Bugzilla 3.2
| Assignee | ||
Comment 1•17 years ago
|
||
Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2. This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.
Target Milestone: Bugzilla 3.2 → ---
| Assignee | ||
Comment 2•16 years ago
|
||
bz_get_field_defs no longer exists. We use Bugzilla.get_fields instead.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•