View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020196 | mantisbt | custom fields | public | 2015-10-14 11:49 | 2015-12-06 02:45 |
| Reporter | vboctor | Assigned To | vboctor | ||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.3.0-beta.3 | ||||
| Target Version | 1.3.0-rc.1 | Fixed in Version | 1.3.0-rc.1 | ||
| Summary | 0020196: Invalid query on issue update due to custom field | ||||
| Description | In some corner cases, the customer hits invalid query which is trying to set the custom field string to null. This is caused in the following case:
In this case, the new custom field value evaluated to default value provided by bug_update.php page which is null. The fix is to change it to ''. | ||||
| Tags | mantishub | ||||
|
MantisBT: master e6873b32 2015-10-14 07:51 Details Diff |
Fix broken issue update page due to custom field In some corner cases, the customer hits invalid query which is trying to set the custom field string to null. This is caused in the following case: - Custom field is visible on update page. - Custom field is not required. - Custom field is of type list. - Custom field doesn't have any value selected. In this case, the new custom field value evaluated to default value provided by bug_update.php page which is null. The fix is to change it to ''. Fixes 0020196 |
Affected Issues 0020196 |
|
| mod - bug_update.php | Diff File | ||
