# Feature OP-9866 - "Display" Name for WP-Status, WP-Type, Custom-Fields ...

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-9866

## 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

*and where it might be useful*

**As** a admin  
**I want to** keep track of possibly a large number of WP-Types and status

I read about a feature request to disable/enable WP-status per project (couldn't find it though) and it was reported to be quite challenging to make it work with workflows and that it undermines the overall idea of one type having the same workflow everywhere.

But, there are cases where one workflow for every project just isn't gonna cut it. So as middle ground I would propose this alternate solution to avoid risking the overview over your setup if you have to create two types of "Bug" (or anything else setup specific). The main downside for me is, that the name of the type/status/custom field might get quite large (for me to keep track and to avoid overlaps). I would be great if I could set a *display name* so the user gets the short top on name.
