Actions
Bug #3899
closedDate fields not storing value properly
Description
This is likely due to the processing of the ajax response causing the value posted to always be null.
Updated by krileon almost 12 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Was due to the IF check in the ajax response not working the same as the display. On userlists the field name is changed so there are no JS conflict issues, but this change isn't needed on profile which was working fine, but the ajax response did not know this.
Updated by krileon almost 12 years ago
- Status changed from Resolved to Closed
- Target version set to 1.4.9
Actions