User Tools

Site Tools


This is an old revision of the document!

Due Date Requirements

Author: Ryan O'Leary


This feature is documented here:

Mantis allows for creation of custom field definitions for bugs. Currently, Mantis implements code allowing configuration of when the each custom field is displayed and when each custom field is a required field. The current configuration 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 the individual mapping of custom field display/require properties with every individual Status.

Database Changes

  • Add a field to the custom_field table to store the serialized array of display options for every status (varchar(255)). This data is stored as a serialized 1-dimensional array in the format a[status_id]=[display_value] where display_value = {0=none;1=display;2=require}. – NOTE: This will limit the amount of statuses to around 27. If we want to support more than 27 Statuses, we should make this a TEXT field instead.
  • Delete the existing fields that are used for display/require properties in the custom_field table. (display_report, display_update, display_resolved, display_closed, require_report, require_update, require_resolved, require_closed).

Configuration Changes

  • Add string $s_edit_custom_field_status_title for the Custom Field Configuration page sub-title.
  • Add strings $s_custom_field_require, $s_custom_field_display, $s_custom_field_none for the Custom Field Configuration column titles.
  • Remove strings $s_custom_field_display_report, $s_custom_field_display_update, $s_custom_field_display_resolved, $s_custom_field_display_closed, $s_custom_field_require_report, $s_custom_field_require_update, $s_custom_field_require_resolved, $s_custom_field_require_closed as they are no longer required.

General Changes

The most visible change to the users is in the configuration of custom fields. Each field now has a table at the bottom showing the mapping of display value to Status. An example is below: <img src=“”>

The setting applies to viewing bugs, updating bugs, and changing status.


Integration Features

Not sure if this is correct, but in the MantisConnect API code, the new field that stores the display value as a serialized array returns it as such. So you'd get something like: “a:10:{i:10;i:2;i:20;i:1;i:30;i:2;i:40;i:2;i:50;i:1;i:60;i:1;i:70;i:2;i:71;i:2;i:72;i:0;i:73;i:0;}”


Please add your comments and feedback in this section.

mantisbt/custom_field_display_requirements.1185743093.txt.gz · Last modified: 2008/10/29 04:31 (external edit)