Project

General

Profile

Actions
Copy link

Feature #9700

closed

Allow to configure the visibility of the fields of the “New issue” form per role

Added by Hugues De Keyzer about 13 years ago. Updated about 13 years ago.

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

0%

Estimated time:
Resolution:
Duplicate

Description

All fields of the “New issue” form are visible to every role. This is not ideal, as a reporter can enter values that normally only a manager or a developer should enter, such as assignee, start and due date, estimated time,… Moreover, it unnecessarily complicates the form for less technical users.

It would be nice to be able to configure the visibility of the fields of this form per role. If configuring the visibility of each field is not feasible, a possibility would be to have a permission to set values for the “advanced” fields. I consider that the basic fields that should always be displayed are:
  • Tracker
  • Subject
  • Description
  • Files (to allow to join screenshots etc.)

All other fields should not be displayed in the form if the user doesn’t have the permission to set them. It should be possible to configure whether custom fields are “basic” or “advanced”.

Related issues

Related to Redmine - Feature #1091: Disabling default ticket fields per trackerClosedJean-Philippe Lang2008-04-23

Actions
Related to Redmine - Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory Closed2011-04-03

Actions
Is duplicate of Redmine - Feature #5011: Limit Visible Issue Fields Based on PermissionsClosed2010-03-08

Actions
Actions
Copy link

Also available in: Atom PDF