# Feature OP-9488 - Cleanup placeholders of editable attributes

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-9488

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 12.3.0 |
| Sprint | 12.3.0 |
| 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 |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a project member  
**I want to** be able to easily identify empty fields in a work package  
**so that** quickly identify if information is missing, and fill them out when that information becomes available

### Acceptance criteria

This work package only concerns the work package form fields, not the new updated sub-header section described in <mention class="mention" data-id="40539" data-type="work_package" data-text="#40539">\#40539</mention>. So for fields that are migrating from the form section to the sub-header, please ignore this rule.

### Acceptance criteria

Having the same placeholder text makes it easier to scan a list of attributes and determine very quickly which ones are filled and which ones are empty. The *type* of field (long text, short, date) is not as relevant pre-interaction, and becomes evident on click/tap.

  - Unify the placeholder for editable attributes that are empty such that they are always represented with a "-"
      - Conserve the "-" placeholder in existing attributes
      - Replace "\<Field name\>: Click to edit..." with "-"
  - When the value is "0", the field is not empty and "0" must then be displayed (with the appropriate unit where appropriate).
  - Give the placeholder a minimum length (existing behaviour) so that the click zone is larger than just the width of the "-"

### ~~Original text (archived 20 Jul)~~

~~Forwarded from a premier customer request:~~

~~The placeholders for editable attribute differ depending on the type of attribute used.~~

~~We often use~~ `~~-~~` ~~but for long text fields, a repeated "\<Field name\>:" followed by "Click to edit..." is used. Would it be possible to make a more consistent choice, and what would that be from a UX perspective.~~

<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/23669/content"></div></figure>