Vote #65389: Permissions for roles to change fields per tracker/status - redmineorg-copy202205 - Redmine

編集操作

リンクをコピー

Vote #65389

完了

Permissions for roles to change fields per tracker/status

Admin Redmine さんが3年以上前に追加. 3年以上前に更新.

ステータス:

Closed

優先度:

通常

担当者:

カテゴリ:

Permissions and roles_17

対象バージョン:

2.1.0_47

開始日:

2009/06/22

期日:

進捗率:

予定工数:

Redmineorg_URL:

https://www.redmine.org/issues/3521

category_id:

version_id:

issue_org_id:

3521

author_id:

6184

assigned_to_id:

comments:

status_id:

tracker_id:

plus1:

affected_version:

closed_on:

affected_version_id:

ステータス-->[Closed]

引用

説明

It would be nice to have (possibly in the same page as the workflow administration) a toggle for a role for a tracker so that updating a field is allowed or disallowed. I.e. since RedMine is already allowing or disallowing the change of the status in the work flow from some previous state to some new state, why not make a simple addition that extends this to any field, but not for every possible state change of those fields, just a simple gating switch of whether or not a change is allowed for that role.

For example, I do not wish developers to be able to move a bug to another version. Right now there is no way to disallow this basically. This should be the function of a manager, who makes the decision together with the stakeholders of whether or not a feature/bug, etc. is moved to a future version.

journals

+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1

very agree with this feature but...
try to take a look at link below.

#5032
#4670
#703
#1091
#4927
#4684
#4309
#3090
--------------------------------------------------------------------------------
related to #8050
--------------------------------------------------------------------------------
Feature added. You can now configure read-only fields per tracker, status and role.

A new tab is added to the workflow settings to configure read-only standard/custom fields. This same form is used to configure required fields as well (#703):

!workflow_permissions.png!

Note that if a user has multiple roles on the same project, only fields that are read-only for all its roles are actually read-only.
--------------------------------------------------------------------------------
is also closing ticket #10697
--------------------------------------------------------------------------------
*I have a question. I want to implement these Feature #3521 in redmine 2.0.1. but it will work ?*

This feature will be very useful in my company. I have no time to wait 45 days for new version 2.1.0. On monday I am starting a new project and I need this feature.
--------------------------------------------------------------------------------
#11887 may be a bug related with this feature
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

related_issues

relates,Closed,8050,Mightful workflow field enhancement: visible, read only and mandatory
relates,Closed,10697,Split role permission for "edit ticket"
relates,New,13814,No more comments when ticket closed
relates,Closed,10922,Allow tracker only for Subtask
relates,Closed,1445,add new permission 'edit issue planning'
relates,Closed,13422,"Edit assigned user" permission for issues
duplicates,Closed,5067,Read only custom field
duplicates,Closed,1919,Separate permissions for changing assigned-to, % finished and target version
duplicates,Closed,8134,Restrict edit issue possibilities per role
duplicates,Closed,7557,Deny editing of descriptions of closed issues
duplicates,Closed,583,Make "Assign To" field read only or disabled for certain roles.
duplicates,Closed,10394,Implement permission "Assign users to issues".
duplicates,Closed,10950,need help add issue without any selection
duplicates,Closed,10684,hide list of assignees when creating new issue
duplicates,Closed,5239,privilege to assign an issue
duplicates,Closed,6036,user permission is changing as the workflow state is changed
duplicates,Closed,6219,More precise "Edit issue" permission
duplicates,Closed,4684,Allow for customizable view permissions when adding an issue