Project

General

Profile

Actions
Copy link

Patch #31954

closed

Reject project/version custom field values not visible to user

Added by Marius BĂLTEANU about 6 years ago. Updated over 5 years ago.

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

0%

Estimated time:

Description

This implements #23997#note-16 for project and version custom fields.

For spent time custom fields, I'll add a new ticket when it'll be ready (some tests fail and need to be updated).

Files

Download all files
0001-Reject-project-custom-field-values-not-visible-for-t.patch (3.09 KB) 0001-Reject-project-custom-field-values-not-visible-for-t.patch Marius BĂLTEANU, 2019-08-27 09:15
0002-Reject-version-custom-field-values-not-visible-for-t.patch (3.5 KB) 0002-Reject-version-custom-field-values-not-visible-for-t.patch Marius BĂLTEANU, 2019-08-27 09:15

Related issues

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

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

Actions
Actions
Copy link

Also available in: Atom PDF