Project

General

Profile

Actions

Feature #3976

closed

Hide custom fields from certain roles

Feature #3976: Hide custom fields from certain roles

Added by Nils Kluge about 17 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Resolution:
Duplicate

Description

It would be a great feature to show/hide custom fields in a project depending on the user's role.

We have some cutomers looking into our projects using the role customer and adding issues (defects / features).

Today we added a custom field that marks an issue as maintenance issue.
But this flag indicates an internal state and should not be seen by the customer.

It would be great to configure the roles that can see a custom field in the project's configuration.


Related issues 3 (2 open — 1 closed)

Related to Redmine - Feature #3088: Estimated hours field able to hide role basedNewActions
Related to Redmine - Feature #7955: Display issue field depending on roleNewActions
Is duplicate of Redmine - Feature #5037: Role-based issue custom field visibilityClosedJean-Philippe LangActions

Updated by Marcel Hochuli almost 16 years ago Actions #1

I would double this feature! Are there plans when this feature will be implemented?

Updated by pasquale [:dedalus] over 15 years ago Actions #2

+1

Updated by Stefan Langenmaier over 15 years ago Actions #3

I have written a plugin for this purpose.

Check it out: https://github.com/stefan-langenmaier/redmine_permits

Updated by James Silver over 13 years ago Actions #4

Definitely need this functionality! We've been trying to figure out a way of adding an additional 'Tags' field allowing us to privately categorize tickets away from the eyes of the client.

We have found a workaround which sort-of works for our use case for the moment (if anyone else needs this):

1. Add #hashtags to your issue in private comments (private comments were added to Redmine in #1554)
2. Use the issue search page to search for these hashtags (only those who are allowed to view private comments will get the search results).

This is obviously a very limited and hacky workaround and is no substitute for proper support for permissions on custom fields, but it may help someone else!

Updated by Wim DePreter over 13 years ago Actions #5

duplicate of #5037 ?

Updated by Toshi MARUYAMA over 13 years ago Actions #6

  • Status changed from New to Needs feedback

Updated by Toshi MARUYAMA over 13 years ago Actions #7

  • Related to Feature #5037: Role-based issue custom field visibility added

Updated by Nils Kluge over 13 years ago Actions #8

Seems to be closed by #5037

Updated by Toshi MARUYAMA over 13 years ago Actions #9

  • Status changed from Needs feedback to Closed
  • Resolution set to Duplicate

Thank you for your feedback.

Updated by Toshi MARUYAMA over 13 years ago Actions #10

  • Related to deleted (Feature #5037: Role-based issue custom field visibility)

Updated by Toshi MARUYAMA over 13 years ago Actions #11

  • Is duplicate of Feature #5037: Role-based issue custom field visibility added
Actions

Also available in: PDF Atom