Project

General

Profile

Actions
Copy link

Defect #19297

closed

Custom fields with hidden/read-only combination displayed in Issue Edit Form

Added by @ go2null almost 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jean-Philippe Lang
Category:
Issues
Target version:
2.6.4
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:
2.6.0

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.)
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
Actions
Copy link
 #1

Updated by Jean-Philippe Lang almost 10 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
Actions
Copy link
 #2

Updated by Jean-Philippe Lang almost 10 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
Copy link

Also available in: Atom PDF