This patch was created on version 1.1.6

It aims at enabling user to parametrize which custom field is displayed and which field is mandatory on status change page depending on the new status.

To install on a version 1.1.6:
1/ either copy all php and txt files included in the zip package to corresponding mantis directory or apply the patch included in the root folder.
2/ Alter database structure: add a field named display_enum of type varchar(255) to mantis_custom_field_table (file readme-migration/upgrade_database_patch.sql gives sql syntax for MS sql server).
3/ put file readme-migration/upgrade_database.php in mantis admin directory and execute it once. This migrate display parametrization from existing configuration.
4/ Alter database structure: remove the following columns from table mantis_custom_field_table (file readme-migration/upgrade_database_patch2.sql gives sql syntax for MS sql server - it might need adaptation):
	- display_report
	- display_update;
	- display_resolved;
	- display_closed;
	- require_report;
	- require_update;
	- require_resolved;
	- require_closed;
5/ customize behavior:
	Default behavior when updating bug is to only display custom fields that are relevant to current status - this can cause troubles in following cases:
	- if there's an error in the value of a custom field that isn't available for the current status, this value can't be modified without changing status.
	- if status changes and field is not displayed in curent status but mandatory in new status: the field can't be filled but update would fail cause the value is missing.
	
	Two workaround are proposed: 
		a/ Display all custom fields on update page: this is enabled by setting parameter $g_custom_fields_update_all to ON in config_inc.php file
		b/ Use a specific status configuration for update that will be used instead of current status to determine wich fields are displayed when updating. This is enabled by setting the parameter $g_custom_field_update_equiv_status in config_inc.php file to a id of a valid status.
		
Notes:
It is based on patch posted by roleary on page http://www.mantisbt.org/bugs/view.php?id=5744 which has been adapted for the following reasons:
- A bug fix: bug view page didn't work in last patch posted by roleary. 
- Viewing Issue page displays all custom values whatever the status, having a custom field value not displayed at all on a specific status would be weird to users.
- Modifying update pages to enable other options than only displaying custom fields depending on status - see above uses cases that wouldn't work properly with default behavior.
- Adaptation to version 1.1.6

Soap API modifications hasn't be tested, updates made by roleary where just kept.