View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012550 | mantisbt | custom fields | public | 2010-11-22 10:22 | 2011-08-05 02:31 |
| Reporter | dandjo | Assigned To | atrol | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Product Version | 1.2.3 | ||||
| Summary | 0012550: custom field required, but not configured as required | ||||
| Description | There's a false behavior when working with custom fields. I defined a custom field and set the following flags to false (not checked): Required On Report [ ] When I have a look in the database these colums (require_report, require_update, require_resolved, require_closed) are set to "0" for this custom field. Now when I report an issue, the error "A necessary field <custom-field-name> was empty. Please recheck your inputs." Bug or misconfiguration? | ||||
| Tags | No tags attached. | ||||
|
Please check: Is this one 0011684 your issue? |
|
|
Yes it is, but I encountered this problem with Enumeration. |
|
|
Yes, enums are also affected |
|