View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0016954 | mantisbt | custom fields | public | 2014-02-11 14:52 | 2019-09-26 16:41 |
Reporter | badfiles | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | duplicate | ||
Product Version | 1.2.17 | ||||
Summary | 0016954: Date type custom field with a default value set might result in application error on a new bug adding | ||||
Description | The issue is conditional | ||||
Steps To Reproduce | Set a default value to a date type custom filed. You will get the bug added with an empty field (just as desired) and the application error shown. | ||||
Tags | No tags attached. | ||||
seems like it's a dupe of 0016952 |
|
This is how I've overridden the problem with an empty date field, but the problem is more complex – an error in a custom field does not prevent new bug to be inserted into the database. https://github.com/badfiles/mantisbt/commit/4bbe25949154849b065f4e94565a2d3c7eb31c7d |
|
Related to 0017354 In file bug_report.php: |
|
Closing as duplicate of 0016952 per 0016954:0039376 |
|