Bug #5422
Required custom fields is not managed
| Status: | New | Start date: | 07/20/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
The fact that a custom field is declared as Required seems not to be managed.
Nothing indicates that the custom field is required (generally indicated by an asterisk) and the custom field can still be saved with a null value.