Project

General

Profile

Actions

Defect #19193

open

Custom Field definition inconsistency

Added by Kiran Kumar over 9 years ago. Updated over 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

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

Has duplicate Redmine - Defect #12940: Workflow permission of "read-only" on required custom fields prevents submission of issuesClosed

Actions
Has duplicate Redmine - Defect #15408: Role-based issue custom field visibility & required field handlingClosed

Actions
Has duplicate Redmine - Defect #20257: Read-only essential custom field at the time of ticket editingClosed

Actions
Has duplicate Redmine - Defect #12954: Required field can't be read-onlyClosed

Actions
Actions

Also available in: Atom PDF