View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0012353 | mantisbt | custom fields | public | 2010-09-15 08:41 | 2011-08-05 02:25 |
Reporter | wmalgadey | Assigned To | atrol | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | duplicate | ||
Product Version | 1.2.2 | ||||
Summary | 0012353: Not requiered custom field got validated on new issue | ||||
Description | I created a custom field (MultiSelect) with following options: Default Value: (one of the MultiSelect-Options) Display When Reporting Issues: false Required On Report: false The Custom Field is linkt to the active project Now I created a new Issue. Filled the non optional fields (categorie, title, description) and saved. I expected that the issue is created with the default value in my custom field. But I got an error reporting the field "xxx" could not be empty! | ||||
Additional Information | I changed the file bug_report.php as following: --- bug_report.php Wed Sep 15 14:27:24 2010
now only custom fields "Required On Report" are beeing checked and the default Values for those custom fields are used again. something which realy bothers me is that the git-repository does not show those errors, but the actual 1.2.3 download did contain it! | ||||
Tags | No tags attached. | ||||