# Feature OP-10868 - Project custom field "Visible" option confusing

Project: OpenProject
Status: needs clarification
URL: https://community.openproject.org/work_packages/OP-10868

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

Project custom fields have a "visible" flag that used to control whether it would show up on the project list. This is now controlled through system settings \> projects.

When visible is checked, only admins are able to see the value in project list and the member widget. It is also no longer available for use in macros (e.g., `projectValue:"Custom field name"` except for admins

I would suggest two options:

**1. Remove flag**

We fully remove the visible flag as it has no use-case anymore

**2. Repurpose flag**

We repurpose the visible flag to do what it says on the documentation: <https://www.openproject.org/docs/system-admin-guide/custom-fields/custom-fields-projects/>

> If you check visible it will also be visible for all users (non-admins) in the project overview and displayed in the project details widget on the Project Overview
