Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit ab0f381

Browse files
committedFeb 28, 2012
Fixed documentation typo for column names
The field name for additional information is additional_info rather than additional_information.
1 parent 7caa180 commit ab0f381

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed
 

‎config_defaults_inc.php

+1-1
Original file line numberDiff line numberDiff line change
@@ -829,7 +829,7 @@
829829
* reproducibility, status, resolution, category_id, date_submitted, last_updated,
830830
* os, os_build, platform, version, fixed_in_version, target_version, view_state,
831831
* summary, sponsorship_total, due_date, description, steps_to_reproduce,
832-
* additional_information, attachment_count, bugnotes_count, selection, edit,
832+
* additional_info, attachment_count, bugnotes_count, selection, edit,
833833
* overdue
834834
*
835835
* @global array $g_view_issues_page_columns

‎docbook/adminguide/en/configuration.sgml

+1-1
Original file line numberDiff line numberDiff line change
@@ -745,7 +745,7 @@
745745
<term>$g_view_issues_page_columns</term>
746746
<listitem>
747747
<para>This configuration option is used to select the columns to be included in the View Issues page and in which order. If one of the column is not accessible to the logged in user, or corresponds to a disabled feature, then it will be automatically removed from the list at runtime. Hence, the same column list may show a different set of columns based on the logged in user, the currently selected project and enabled features (e.g. sponsorship_total is only shown if the sponsorship feature is enabled).</para>
748-
<para>The supported columns are: selection, edit, id, project_id, reporter_id, handler_id, priority, reproducibility, projection, eta, resolution, fixed_in_version, view_state, os, os_build, build (for product build), platform, version, date_submitted, attachment_count, category, sponsorship_total, severity, status, last_updated, summary, bugnotes_count, description, steps_to_reproduce, additional_information. As for custom fields they can be referenced by adding a 'custom_' to their name (e.g. xyz would be custom_xyz).</para>
748+
<para>The supported columns are: selection, edit, id, project_id, reporter_id, handler_id, priority, reproducibility, projection, eta, resolution, fixed_in_version, view_state, os, os_build, build (for product build), platform, version, date_submitted, attachment_count, category, sponsorship_total, severity, status, last_updated, summary, bugnotes_count, description, steps_to_reproduce, additional_info. As for custom fields they can be referenced by adding a 'custom_' to their name (e.g. xyz would be custom_xyz).</para>
749749
<para>By default the following columns are selected: selection, edit, priority, id, sponsorship_total, bugnotes_count, attachment_count, category_id, severity, status, last_updated, summary.</para>
750750
</listitem>
751751
</varlistentry>

1 commit comments

Comments
 (1)

atrol commented on Feb 28, 2012

@atrol
Member

Quite confusing because there are various places where you have to use additional_information
Seems that the documentation was OK for all *_columns but not for *_fields

For example you have to use "additional_info" to customize $g_bug_report_page_fields but
"additional_information" to customize $g_view_issues_page_columns

Please sign in to comment.