View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0022663 | mantisbt | custom fields | public | 2017-04-04 06:02 | 2017-04-30 14:48 |
Reporter | lbayle2 | Assigned To | syncguru | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | open | ||
Product Version | 2.3.0 | ||||
Target Version | 2.3.2 | Fixed in Version | 2.3.2 | ||
Summary | 0022663: APPLICATION ERROR 1303 Non-mandatory date custom fields blocking issue creation | ||||
Description | Usecase:
APPLICATION ERROR 0001303 bug does not exist on v2.2.1 | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
related to | 0022653 | closed | cproensa | Regression: Filter by date broken |
has duplicate | 0022706 | closed | ERROR 1303 invalid value for field (Custom Field date) | |
has duplicate | 0022726 | closed | atrol | APPLICATION ERROR 0001303; Custom date field |
has duplicate | 0022758 | closed | atrol | AFter updating to v2.3.1 Custom Field in bugs are not editable |
Seeing this as well |
|
Hello. |
|
The reverts applied to to 2.3.1 did leave one line out (don't know why though) |
|