# Feature OP-13025 - Define fields to be writeable in read-only states

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 2 |
| 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

**As** a *project manager*  
**I want to** *define certain fields to be editable even in a read-only state*  
**so that** *I can allow editing specific information.*

*real world example: I have a field for "next review" which is a date on which a closed feature shall be reviewed, in case any changes are required or an improvement could be done (following a PDCA cycle). This date can't be changed if the work package is read-only. But I need to be able to change the review date, so that I can terminate a new date once a review has been done. The remainder of the ticket needs to stay intact and no information should be changed though.*

**Acceptance criteria**

  - enhance the status configuration to allow selecting writeable fields in the "Work package read-only" section
