Project

General

Custom queries



Profile

Actions

Feature #23997

closed

Per role visibility settings for version custom fields

Added by Jens Krämer over 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Custom fields
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

For issue custom fields, one can already select which roles should be allowed to view this field.

This patch, developed at Planio and sponsored by SDZeCOM GmbH, introduces the same setting for project and version custom fields.


Files


Related issues

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

Actions
Related to Redmine - Feature #31859: Per role visibility settings for spent time custom fieldsClosedGo MAEDA

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

Actions
Related to Redmine - Patch #31954: Reject project/version custom field values not visible to userClosedGo MAEDA

Actions
Has duplicate Redmine - Feature #15416: Role-based issue custom field visibility for projectsClosed

Actions
#1

Updated by Jan from Planio www.plan.io over 8 years ago

  • Target version set to Candidate for next minor release
#2

Updated by Jens Krämer over 8 years ago

#3

Updated by Toshi MARUYAMA over 8 years ago

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

Updated by Go MAEDA almost 6 years ago

  • Category set to Custom fields
#7

Updated by Go MAEDA over 5 years ago

  • Has duplicate Feature #15416: Role-based issue custom field visibility for projects added
#8

Updated by Marius BĂLTEANU over 5 years ago

  • Related to Feature #31859: Per role visibility settings for spent time custom fields added
#9

Updated by Marius BĂLTEANU over 5 years ago

  • Assignee set to Marius BĂLTEANU
#11

Updated by Marius BĂLTEANU over 5 years ago

#14

Updated by Marius BĂLTEANU over 5 years ago

  • Related to Feature #31925: Per role visibility settings for project custom fields added
#15

Updated by Marius BĂLTEANU over 5 years ago

#17

Updated by Marius BĂLTEANU over 5 years ago

  • Assignee deleted (Marius BĂLTEANU)
  • Target version changed from Candidate for next minor release to 4.1.0
#18

Updated by Go MAEDA over 5 years ago

  • Status changed from New to Closed
  • Assignee set to Go MAEDA
#19

Updated by Marius BĂLTEANU over 5 years ago

  • Related to Patch #31954: Reject project/version custom field values not visible to user added
#20

Updated by Jean-Philippe Lang over 5 years ago

  • Tracker changed from Patch to Feature
Actions

Also available in: Atom PDF