Project

General

Profile

Actions

Feature #5037

closed

Role-based issue custom field visibility

Added by Dario Laera over 14 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Category:
Issues permissions
Target version:
Start date:
2010-03-10
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

It would be nice to define some kind of view permission for fields in issues. For example, when you define a new custom field you should define also wich role can view this field.
The implementation of #337 should open the way for implementing this feature too.


Files

2014-07-17 09_13_13-Workflow.png (15.9 KB) 2014-07-17 09_13_13-Workflow.png Juozapis Juozapauskiksi, 2014-07-17 08:21

Related issues

Related to Redmine - Feature #5011: Limit Visible Issue Fields Based on PermissionsClosed2010-03-08

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

Actions
Related to Redmine - Feature #14162: Hidden Fields - Role BasedClosed

Actions
Related to Redmine - Defect #17096: Issue emails cannot be threaded by some mailers due to inconsistent Message-ID and References fieldClosedGo MAEDA

Actions
Related to Redmine - Feature #23997: Per role visibility settings for version custom fieldsClosedGo MAEDA

Actions
Related to Redmine - Patch #29160: Remove unused and broken method CustomField.visibility_conditionClosedJean-Philippe Lang

Actions
Has duplicate Redmine - Feature #8162: Issue custom field visibility per workflowClosed2011-04-15

Actions
Has duplicate Redmine - Feature #3976: Hide custom fields from certain rolesClosed2009-10-06

Actions
Actions

Also available in: Atom PDF