Defect #19193
open
Custom Field definition inconsistency
Description
The custom fields allow us to create a field as 'required' and also allow us to set the visibility per role. But it still mandates the field entry for other users to whom it is not visible.
This behavior is inconsistent. Please correct it at the earliest as we need such a customization for our project.
Related issues
Updated by Jan Niggemann (redmine.org team member) almost 11 years ago
Kiran Kumar wrote:
Please correct it at the earliest as we need such a customization for our project.
We strive to fix issues as fast as possible. Redmine is free software and developed as open source. We dedicate our free time to the project, so fixing this may (or may not) need quite a lot of time, depending on the severity of the issue and the ease of creating a solution.
If you really need a fix in a timely manner, it would probably be best you fix the underlying issue and submit a patch.
Updated by Go MAEDA about 9 years ago
- Has duplicate Defect #12940: Workflow permission of "read-only" on required custom fields prevents submission of issues added
Updated by Go MAEDA about 9 years ago
- Has duplicate Defect #15408: Role-based issue custom field visibility & required field handling added
Updated by Go MAEDA about 9 years ago
- Has duplicate Defect #20257: Read-only essential custom field at the time of ticket editing added
Updated by Go MAEDA about 9 years ago
- Has duplicate Defect #12954: Required field can't be read-only added