fields.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
 <!ENTITY % BOOK_ENTITIES SYSTEM "Admin_Guide.ent">
]>
<section id="admin.config.fields">
	<title>Field Visibility</title>

	<variablelist>
		<varlistentry>
			<term>$g_enable_eta</term>
			<listitem>
				<para>
					Enable or disable usage of 'ETA' field.  Default value is OFF.
				</para>
			</listitem>
		</varlistentry>
		<varlistentry>
			<term>$g_enable_projection</term>
			<listitem>
				<para>
					Enable or disable usage of 'Projection' field.  Default value is OFF.
				</para>
			</listitem>
		</varlistentry>
		<varlistentry>
			<term>$g_enable_product_build</term>
			<listitem>
				<para>
					Enable or disable usage of 'Product Build' field.  Default is OFF.
				</para>
			</listitem>
		</varlistentry>
		<varlistentry>
			<term>$g_bug_report_page_fields</term>
			<listitem>
				<para>
					An array of optional fields to show on the bug report page.
				</para>
				<para>
					The following optional fields are allowed:
					additional_info,
					attachments,
					category_id,
					due_date,
					handler,
					monitors,
					os,
					os_version,
					platform,
					priority,
					product_build,
					product_version,
					reproducibility,
					resolution,
					severity,
					status,
					steps_to_reproduce,
					tags,
					target_version,
					view_state.
				</para>
				<para>
					The summary and description fields are always shown
					and do not need to be listed in this option. Fields
					not listed above cannot be shown on the bug report
					page. Visibility of custom fields is handled via the
					Manage =&gt; Manage Custom Fields administrator page.
				</para>
				<para>Note that <emphasis>monitors</emphasis> is not an actual
					field; adding it to the list will let authorized reporters
					(see <emphasis>monitor_add_others_bug_threshold</emphasis>
					in <xref linkend="admin.config.misc" />)
					select users to add to the issue's monitoring list.
					Monitors will only be notified of the submission if both
					their e-mail preferencess and the <emphasis>notify_flags</emphasis>
					configuration (see <xref linkend="admin.config.email" />)
					allows it, i.e.
					<programlisting>$g_notify_flags['new']['monitor'] = ON;</programlisting>
				</para>
				<para>
					This setting can be set on a per-project basis by
					using the Manage =&gt; Manage Configuration
					administrator page.
				</para>
			</listitem>
		</varlistentry>
		<varlistentry>
			<term>$g_bug_view_page_fields</term>
			<listitem>
				<para>
					An array of optional fields to show on the issue view page and other pages that include issue details.
				</para>
				<para>
					The following optional fields are allowed:
					additional_info,
					attachments,
					category_id,
					date_submitted,
					description,
					due_date,
					eta,
					fixed_in_version,
					handler,
					id,
					last_updated,
					os,
					os_version,
					platform,
					priority,
					product_build,
					product_version,
					project,
					projection,
					reporter,
					reproducibility,
					resolution,
					severity,
					status,
					steps_to_reproduce,
					summary,
					tags,
					target_version,
					view_state.
				</para>
				<para>
					Fields not listed above cannot be shown on the bug
					view page. Visibility of custom fields is handled via
					the Manage =&gt; Manage Custom Fields administrator page.
				</para>
				<para>
					This setting can be set on a per-project basis by
					using the Manage =&gt; Manage Configuration
					administrator page.
				</para>
			</listitem>
		</varlistentry>
		<varlistentry>
			<term>$g_bug_update_page_fields</term>
			<listitem>
				<para>
					An array of optional fields to show on the bug update page.
				</para>
				<para>
					The following optional fields are allowed:
					additional_info,
					category_id,
					date_submitted,
					description,
					due_date,
					eta,
					fixed_in_version,
					handler,
					id,
					last_updated,
					os,
					os_version,
					platform,
					priority,
					product_build,
					product_version,
					project,
					projection,
					reporter,
					reproducibility,
					resolution,
					severity,
					status,
					steps_to_reproduce,
					summary,
					target_version,
					view_state.
				</para>
				<para>
					Fields not listed above cannot be shown on the bug
					update page. Visibility of custom fields is handled
					via the Manage =&gt; Manage Custom Fields administrator
					page.
				</para>
				<para>
					This setting can be set on a per-project basis by
					using the Manage =&gt; Manage Configuration
					administrator page.
				</para>
			</listitem>
		</varlistentry>
	</variablelist>
</section>