mantisbt:custom_field_display_requirements
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
mantisbt:custom_field_display_requirements [2007/07/30 21:40] – added comments thraxisp | mantisbt:custom_field_display_requirements [2007/08/07 14:31] – roleary | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Custom Field Display Requirements ====== | ||
- | **Author:** Ryan O' | ||
- | |||
- | ===== Introduction ===== | ||
- | |||
- | This feature is documented here: http:// | ||
- | |||
- | 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/ | ||
- | |||
- | This feature will allow the individual mapping of custom field display/ | ||
- | |||
- | ===== 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; | ||
- | * Delete the existing fields that are used for display/ | ||
- | |||
- | ===== Configuration Changes ===== | ||
- | |||
- | * Add string $s_edit_custom_field_status_title for the Custom Field Configuration page sub-title. | ||
- | * Add strings $s_custom_field_require, | ||
- | * Remove strings $s_custom_field_display_report, | ||
- | |||
- | ===== 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 here: | ||
- | {{: | ||
- | |||
- | The setting applies to viewing bugs, updating bugs, and changing status. | ||
- | |||
- | ===== Reminders ===== | ||
- | |||
- | As part of the patch attached to bug 5744, I've added a function called migrateCustomFieldDisplay(). This function will take the current custom fields settings using the display_ and require_ fields and transition them to the new display setting array. In the patch, the function is never called. During an upgrade, the function needs to be called AFTER the php patches have been applied, AFTER the new field has been added to the custom_field table, and BEFORE the old display_ and require_ fields are removed from the custom_field table. | ||
- | |||
- | The strings specified above that were removed, were only removed from the strings_english.txt file, not any of the other languages. Same with the strings added. | ||
- | |||
- | ===== 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: " | ||
- | |||
- | ===== Feedback ===== | ||
- | |||
- | thraxisp - What happened to the ' | ||
- | |||
- | thraxisp - I assume that the visibility by access level is retained. That is, viewer can't see fields with the read parameter set to a higher level. | ||
- | |||
- | |||
- | |||
- | Please add your comments and feedback in this section. |
mantisbt/custom_field_display_requirements.txt · Last modified: 2008/10/29 04:25 by 127.0.0.1