Feature #15416

Role-based issue custom field visibility for projects

Added by Christoph Klesser about 6 years ago. Updated 6 months ago.

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

0%

Category:Project settings
Target version:-
Resolution:Duplicate

Description

Now, with #5037, custom fields inside issues can be restricted for certain roles. Thanks everybody involved for implementing that very useful feature!

However, such restricted fields can only be added to issues now, but not to projects, for example. It would be great for our organization to, for example, also add information to projects that are not visible for everybody involved, like project budgets, informal agreements etc.


Related issues

Duplicates Redmine - Feature #23997: Per role visibility settings for version custom fields Closed

History

#1 Updated by Maksim Kuzmin over 4 years ago

Can we expect that will be the update ?

#2 Updated by Alexis Parent over 4 years ago

+1

#3 Updated by Stephane Evr over 3 years ago

+1!

#4 Updated by Adriano Carneiro over 3 years ago

+100

#5 Updated by Kush Suryavanshi over 3 years ago

+1

#6 Updated by Kush Suryavanshi over 3 years ago

For what it's worth, I was able to achieve this by changing the source code. It's not an elegant solution, but it suffices my needs now. I <3 open source.

#7 Updated by Mariusz Zielinski over 2 years ago

+2 Agree, This could be very usefull feature.

#8 Updated by Go MAEDA 6 months ago

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

#9 Updated by Go MAEDA 6 months ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Patch #23997 includes this feature.

Also available in: Atom PDF