User Tools

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

Site Tools


mantisbt:custom_field_display_requirements

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
mantisbt:custom_field_display_requirements [2007/07/29 17:04] rolearymantisbt:custom_field_display_requirements [2008/10/29 04:25] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== Due Date Requirements ======+====== Custom Field Display Requirements ======
  
 **Author:** Ryan O'Leary **Author:** Ryan O'Leary
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 below+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
-<img src="http://www.ryanoleary.net/mantisbt_5744.jpg">+{{:mantisbt:mantisbt_5744.jpg|:mantisbt:mantisbt_5744.jpg}}
  
 The setting applies to viewing bugs, updating bugs, and changing status. The setting applies to viewing bugs, updating bugs, and changing status.
Line 31: Line 31:
 ===== 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: "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;}" 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;}"
 +
 +
  
 ===== Feedback ===== ===== Feedback =====
  
-Please add your comments and feedback in this section.+thraxisp - What happened to the 'Advanced' setting? This controlled fields that were displayed on the Advanced pages.  
 +  * roleary - The Advanced setting is still available (it's above the screenshot that I attached). However, I believe that "paulr" has taken my patch and is modifying it, and that the Advanced setting is something he's changing. Part of this is because it obviously doesn't make sense to have a field 'Required' and 'Display only on Advanced'. When he finishes his update, I'll change this page. 
 +----
  
 +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 'Required'. In that case, it actually wouldn't get checked because it wouldn't have been displayed... I think. This issue will probably also be resolved by paulr's changes.
 +----
  
 +
 +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

Driven by DokuWiki