Closed Bug 545766 Opened 10 years ago Closed 10 years ago
Figure out what columns can be reported on from the database, instead of from a static list
Right now, report.cgi has a static list of columns that can be reported on. Instead of having that static list, it should determine which columns can be reported on via the database. I suspect that this is just all the columns with "buglist => 1" minus a certain subset, although if it becomes complex we could add a "report" or "report_axis" column to fielddefs.
This modifies report.cgi and the template to use a new variable, REPORT_COLUMNS, from Search.pm. This adds a lot of new axises. Some of them have questionable value (like Summary) but who knows, somebody might want to use them....
Assignee: charting → mkanat
Status: NEW → ASSIGNED
Attachment #453956 - Flags: review?(LpSolit)
Attachment #453956 - Flags: review?(LpSolit) → review?(bugzilla)
Comment on attachment 453956 [details] [diff] [review] v1 r=glob
Attachment #453956 - Flags: review?(bugzilla) → review+
Committing to: bzr+ssh://bzr.mozilla.org/bugzilla/trunk/ modified report.cgi modified Bugzilla/Search.pm modified Bugzilla/Template.pm modified template/en/default/global/field-descs.none.tmpl modified template/en/default/search/search-report-select.html.tmpl Committed revision 7258.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.