Project

General

Profile

Actions

Feature #28150

open

Ability to choose Fields permissions for new issue

Added by Aleksandar Pavic about 6 years ago. Updated 15 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues workflow
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

Fields permissions, are missing a setting, in a same way as status transmissions.

If you take a look at Status transitions, vs Fields permissions, you will see that Fields permissions are missing settings if user is author,
nd when user is assignee.

It is also missing a setting for field visibility for special status New issue, which is available for Status transitions.

Currently it means that author can change issue attributes, as long as issue is in same status.
But desired behaviour is to have author enter issue attributes only once, and later he can't change them, or anyone else from some
specific role, unless there are special settings if user is author or assignee...

Just like on Status transitions.


Related issues

Related to Redmine - Defect #34778: Inconsistencies working with workflow permissionsConfirmed

Actions
Actions #1

Updated by Carrie Wang almost 3 years ago

+1

Actions #2

Updated by Albrecht Dreß over 2 years ago

+1

I'm running Redmine 4.0.7 on Debian Buster. At least a patch adding the possibility to block certain issues fields for some roles when a new ticket is created would be highly appreciated!

Actions #3

Updated by Maurizio Andres Baggio over 2 years ago

+1
This would be a really helpful setting

Actions #4

Updated by Go MAEDA about 2 years ago

  • Related to Defect #34778: Inconsistencies working with workflow permissions added
Actions #5

Updated by Will M 15 days ago

+1
Status Transitions has it.
Field Permissions needs it.

Actions

Also available in: Atom PDF