Feature #31925

Per role visibility settings for project custom fields

Added by Marius BALTEANU about 2 years ago. Updated about 2 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Go MAEDA% Done:

0%

Category:Custom fields
Target version:4.1.0
Resolution:Fixed

Description

Extracted the patch from #23997.

0001-Per-role-visibility-settings-for-project-custom-fiel.patch Magnifier (4.5 KB) Marius BALTEANU, 2019-08-19 22:17

Related issues

Related to Redmine - Feature #23997: Per role visibility settings for version custom fields Closed
Related to Redmine - Patch #31954: Reject project/version custom field values not visible to... Closed

Associated revisions

Revision 18379
Added by Go MAEDA about 2 years ago

Per role visibility settings for project custom fields (#31925).

Patch by Jens Krämer and Marius BALTEANU.

Revision 18401
Added by Go MAEDA about 2 years ago

Reject project custom field values not visible for the user (#31954, #31925).

Patch by Marius BALTEANU.

History

#2 Updated by Marius BALTEANU about 2 years ago

  • Related to Feature #23997: Per role visibility settings for version custom fields added

#3 Updated by Go MAEDA about 2 years ago

  • Status changed from New to Closed
  • Assignee set to Go MAEDA
  • Target version changed from Candidate for next major release to 4.1.0
  • Resolution set to Fixed

Committed the patch. Thank you for adding a nice feature!

#4 Updated by Marius BALTEANU about 2 years ago

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

Also available in: Atom PDF