Bug #4233
closed
Fields not accessible can't be conditioned
Added by krileon about 11 years ago.
Updated about 11 years ago.
Start date:
06 September 2013
Description
If you condition off a field that is on a tab accessible only to Special then the value will always be NULL. This is because the POST value is NULL and the getFields value is NULL. It should fallback to grabbing its value from user object if all of the above result in null.
It should ignore this for checkbox fields. Checkbox fields when unchecked are actually set to NULL making this check pretty much impossible.
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Fixed by cloning cbUser then populating with postUser then calling getFields. This now does proper field value checking. As a fallback if the value is null it'll fallback to grabbing from existing user object instead of post user object.
- Target version set to 3.0.11
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by