Closed Bug 1560245 Opened 1 year ago Closed 1 year ago

Specify missing bug field types


( :: General, task)

Not set





(Reporter: kohei.yoshino, Assigned: kohei.yoshino)




(1 file, 1 obsolete file)

46 bytes, text/x-github-pull-request
Details | Review

In Bug 1529362, I’m creating Ajax-based completely new bug lists, which are currently dead plain tables. I need to know the type of each field so the display values can be enriched, but most fields don’t have the type specified. Will send a PR shortly.

Attached file GitHub Pull Request (obsolete) —
Attached file GitHub Pull Request
Attachment #9072989 - Attachment is obsolete: true

Merged to master.

Closed: 1 year ago
Resolution: --- → FIXED

Just a sanity check - and perhaps this isn't the right bug to ask this (though the linked-to bug 1529362 clearly isn't the right place, either) - but how will this cope with Bugzilla extensions that add custom fields and which don't specify a field type?

I know that a type should be specified, but if Bugzilla doesn't enforce this (which I assume it doesn't, based on this commit) then you can be sure there are extensions which leave it unspecified. You'll need to ensure the new Bugzilla doesn't blow up when it encounters this situation.

Many fields in the core and extensions are still without any type, and it won’t be a big problem. By specifying a type, the field will get a proper presentation and sort order on the new search results page, so it’s a good idea to always do so.

OK - that sounds fine. Just making sure that someone had considered this... sounds like you have! :-)

You need to log in before you can comment on or make changes to this bug.