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/08/07 14:28] – roleary | mantisbt:custom_field_display_requirements [2008/10/29 04:25] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 38: | Line 38: | ||
| 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: " | 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: " | ||
| + | |||
| Line 43: | Line 44: | ||
| thraxisp - What happened to the ' | 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. | 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. | Please add your comments and feedback in this section. | ||
mantisbt/custom_field_display_requirements.1186511321.txt.gz · Last modified: 2008/10/29 04:31 (external edit)