Feature #5011


Limit Visible Issue Fields Based on Permissions

Added by Edward Krufka over 13 years ago. Updated about 11 years ago.

Issues permissions
Target version:
Start date:
Due date:
% Done:


Estimated time:


Allow the ADMIN to configure which fields appear when creating/viewing/editing an issue, based on the permissions of the logged in user.

A coy should only copy the fields that the user copying the issue can see in the display.

For instance, allow the developers to enter comments in fields on an issue but do not have these fields appear for the client.

Adding a feature like this would negate the need for Redmine to instruct folks entering issues to not use the Assigned-To field, as that field should not be visible to all folks reporting issues or requesting features.

Related issues

Related to Redmine - Feature #5037: Role-based issue custom field visibilityClosedJean-Philippe Lang2010-03-10

Related to Redmine - Feature #12005: Mightful workflow field enhancement: hideNew

Has duplicate Redmine - Feature #9700: Allow to configure the visibility of the fields of the “New issue” form per roleClosed

Actions #1

Updated by Walther Lalk over 13 years ago

Doing the much hated +1 here.

I would love to see this feature in a future version of Redmine. We are currently incorporating Redmine into our project workflow and the only thing that is missing is the ability to set which fields a user can access when creating a new issue.

In our case we don't want our clients to be able to set the 'assign to', due dates, % done, etc.

Actions #2

Updated by Eric Davis over 13 years ago

  • Category changed from Administration to Issues permissions
  • Priority changed from High to Normal
Actions #3

Updated by pasquale [:dedalus] over 12 years ago


We have various related\dupes tickets on this: it's seems that more users want to manage "native\custom field by role"!

Actions #4

Updated by anonymous incognito over 12 years ago

What, the issue has been there for a whole year yet nobody has bothered to fix it? Not cool, people, there's lots of serious organisations using this software, can't just ignore everyone, you know?

Actions #5

Updated by Terence Mill over 12 years ago

dupes some parts of #8050

Actions #6

Updated by @ go2null about 11 years ago

Should be considered a duplicate of Feature #12005.

Actions #7

Updated by @ go2null about 11 years ago

  • Status changed from New to Resolved

Should be considered a duplicate of Feature #12005.

Actions #8

Updated by Daniel Felix about 11 years ago

Closed as duplicate of #12005. Thanks!

Actions #9

Updated by Daniel Felix about 11 years ago

  • Status changed from Resolved to Closed
  • Resolution set to Duplicate

Also available in: Atom PDF