Vote #76146
完了Custom fields with hidden/read-only combination displayed in Issue Edit Form
開始日:
2022/05/09
期日:
進捗率:
0%
予定工数:
Redmineorg_URL:
category_id:
2
version_id:
93
issue_org_id:
19297
author_id:
54354
assigned_to_id:
1
comments:
2
status_id:
5
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
81
説明
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.)
Desired/Expected Behavior
- In the Issue Edit form, CustomFieldA should not be displayed.
Workaround
- 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
journals
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
いいね!0