mantisbt:custom_field_display_requirements
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
mantisbt:custom_field_display_requirements [2007/07/29 16:35] – roleary | mantisbt:custom_field_display_requirements [2008/10/29 04:25] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
**Author:** Ryan O' | **Author:** Ryan O' | ||
Line 13: | Line 13: | ||
===== Database Changes ===== | ===== Database Changes ===== | ||
- | * Add a field to the custom_field table to store the serialized array of display options for every status (varchar(255)) -- NOTE: This will limit the amount of statuses to around | + | * 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/ | * Delete the existing fields that are used for display/ | ||
Line 24: | Line 24: | ||
===== General Changes ===== | ===== 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 ===== | ===== 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 ===== | ===== 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 ===== | ===== Feedback ===== | ||
- | Please add your comments | + | thraxisp - What happened to the ' |
+ | * roleary - The Advanced setting is still available (it's above the screenshot that I attached). However, I believe that " | ||
+ | ---- | ||
+ | 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. | ||
+ | * roleary - The visibility of fields is retained. Again, this could lead to a business rule issue where a field is not visible, but has been marked as ' | ||
+ | ---- | ||
+ | |||
+ | Please add your comments and feedback in this section. |
mantisbt/custom_field_display_requirements.1185741322.txt.gz · Last modified: 2008/10/29 04:31 (external edit)