• Author: Daryn Warriner (daryn)
• Status: Work in progress, Draft
• Associated Issue: #5650, #4736, #5744

Mantis allows for creation of custom field definitions for bugs. Currently, Mantis allows users to configure when each custom field is displayed and when it is required. The current implementation allows the user to specify the display/require option on 4 conditions; report, update, resolved, closed. The report, resolved, and closed conditions each map to one Status. The update conditions maps to all other statuses.

This feature will allow advanced configuration of custom fields by providing the ability to define complex custom rules using not only any status but also any standard field in scope, any custom field, or any configuration option. In addition, users will be able to apply these custom rules to standard fields as well as custom fields.

• Some notes

• Required database changes to mantis_XXX_table

• New Tables:
  • Create Table mantis_config_actions_table
  • Create Table mantis_config_pages_table
  • Create Table mantis_field_rule_config_table
  • Create Table mantis_field_rule_definition_table
  • Create Table mantis_field_rule_definition_table
  • Create Table mantis_field_rule_link_table
  • Create Table mantis_field_ruleset_action_table
  • Create Table mantis_field_ruleset_operators_table
  • Create Table mantis_field_ruleset_table

• $g_var indicates something

• Please provide feedback