Actions
Defect #19297
closedCustom fields with hidden/read-only combination displayed in Issue Edit Form
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Affected version:
Description
Observed Behavior
- UserA has two roles, RoleA and RoleB.
- CustomFieldA is hidden from RoleB. (In Custom Field Edit form, RoleB is unchecked for Visible.)
- However, CustomFieldA is visible to RoleA.
- In the Workflow, CustomFieldA is set as
Read-Only
for RoleA. - UserA can edit TrackerA.
- In the Issue Edit form, CustomFieldA is displayed. However, any input is ignored (as the
Read-Only
rule prevents it from being processed.)
- In the Issue Edit form, CustomFieldA should not be displayed.
- Allow RoleB to view CustomFieldA.
- In the Workflow, set CustomFieldA as
Read-Only
for RoleB. - The UI code correctly does not display
Read-Only
fields.
Environment: Redmine version 2.6.0.stable Ruby version 1.9.3-p484 (2013-11-22) [x86_64-linux] Rails version 3.2.19 Environment production Database adapter Mysql2
Updated by Jean-Philippe Lang over 9 years ago
- Subject changed from Hidden custom fields displayed in Issue Edit Form to Custom fields with hidden/read-only combination displayed in Issue Edit Form
- Status changed from New to Confirmed
- Target version set to Candidate for next minor release
Updated by Jean-Philippe Lang over 9 years ago
- Status changed from Confirmed to Closed
- Assignee set to Jean-Philippe Lang
- Target version changed from Candidate for next minor release to 2.6.4
- Resolution set to Fixed
Actions