User Tools

  • Logged in as: anonymous (anonymous)
  • Log Out

Site Tools


mantisbt:alternative_custom_field_display_requirements

This is an old revision of the document!


Custom Rules Requirements (Alternative to Custom Field Display Requirements)

Introduction

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.

Implementation Notes

  • Some notes

Database Changes

  • Required database changes to mantis_XXX_table
  • New Tables:
    • mantis_config_actions_table
    • mantis_config_pages_table
    • mantis_field_rule_config_table
    • mantis_field_rule_definition_table
    • mantis_field_rule_definition_table
    • mantis_field_rule_link_table
    • mantis_field_ruleset_action_table
    • mantis_field_ruleset_operators_table
    • mantis_field_ruleset_table

Configuration

  • $g_var indicates something

Implementation Log

Other Changes

Feedback

  • Please provide feedback
mantisbt/alternative_custom_field_display_requirements.1202155055.txt.gz · Last modified: 2008/10/29 04:31 (external edit)

Driven by DokuWiki