Patch #23997

Per role visibility settings for project and version custom fields

Added by Jens Krämer almost 3 years ago. Updated 3 months ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Custom fields
Target version:Candidate for next minor release

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.

0001-per-role-visibility-settings-for-project-and-version.patch Magnifier (9.7 KB) Jens Krämer, 2016-10-05 04:38

0001-per-role-visibility-settings-for-project-and-version.patch Magnifier - updated patch (9.9 KB) Jens Krämer, 2016-10-05 11:06


Related issues

Related to Redmine - Feature #5037: Role-based issue custom field visibility Closed 2010-03-10

History

#1 Updated by Jan from Planio www.plan.io almost 3 years ago

  • Target version set to Candidate for next minor release

#2 Updated by Jens Krämer almost 3 years ago

turns out the patch led to invalid SQL for project custom fields, here is an updated version which overrides CustomField#visibility_by_project_condition in ProjectCustomField to work with the correct project_key (that is, projects.id instead of projects.project_id).

#3 Updated by Toshi MARUYAMA over 2 years ago

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

#4 Updated by Toshi MARUYAMA over 2 years ago

Could you add tests like r12012?

#5 Updated by Mariusz Zielinski about 2 years ago

Hello,
When we may expect custome fields per role visibility available? (this could be really powerfull feature)

#6 Updated by Go MAEDA 3 months ago

  • Category set to Custom fields

Also available in: Atom PDF