Redmine

Basis the review of an earlier defect Defect #41247 response provided to user

Redmine applies the most-open rules for fields permissions to users.

If a user has multiple roles in a project, they can edit the field if any of the roles allows editing the field. Similarly, they can leave the field unset if any of the user's roles does not enforce the field to be required.
h3.
(the user I have created has only one role: Tester)

Please check all of the roles for the user in the project. If you still observe the issue, please provide detailed information about the roles of the user in the project, details about the fields permission settings for all of these roles, as well as details about the specific issue (given that the permissions are specific to a specific tracker and status).

I have created a field: Origin/ type which is made visible to
- all roles
- selected trackers
- all projects

I have created users which are mapped to a single role only
Under Roles & Permission for Tester (as a Role) mapped to Tester as a User:
Against the Issue Tracker I have marked View/ Add/ Edit Issues as Yes

In the Workflow definitions for the Role Tester; Under the Issue Status In Progress (Open--In Progress); I have marked the field Origin/Type as Read Only, since I do not want the user to change the field while working on the Issue.

The Issue is created by a separate user (Admin) and assigned to Tester. When the tester selects the Issue in the In Progress state the field Issue/ type disappears from the screen; instead of being in disabled mode.

Environment Details
nvironment:
Redmine version 6.0.5.stable
Ruby version 3.3.7-p123 (2025-01-15) [x86_64-linux-gnu]
Rails version 7.2.2.1
Environment production
Database adapter Mysql2
Mailer queue ActiveJob::QueueAdapters::AsyncAdapter
Mailer delivery smtp
Redmine settings:
Redmine theme Default
SCM:
Subversion 1.14.5
Git 2.48.1
Filesystem
Redmine plugins:
custom_tables 1.1.1
periodictask 6.0.0
redmine_charts_plugin 1.0.0
redmine_custom_workflows 3.0.1
redmine_email_login 0.0.4

Thanks for the update.

Request if you can share some examples of how to define trackers to indicate segregation between display and update sections.

Able to get the resolution.
All fields would be visible to the user as read only in the displayed issue, however when the user selects edit only those fields that are marked editable would be available for edit.

Thanks.