# Feature OP-18716 - Work package field completion entry criteria for each status

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| 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** an administrator  
**I want to** be able to define which standard and custom fields MUST be completed before the next status becomes available  
**so that** we can ensure key gate criteria / documentation is captured in alignment with our business processes

**Acceptance criteria**

*   Administration section provides a method to allow system owners to specify which fields are required at each status:
    
    *   i.e
        
        *   In **NEW** status only a title is required before being allowed to move to **SPECIFICATION**
            
        *   During **SPECIFICATION** the user must complete **Identified actions** (custom field), set an **End date** and select **Approved by** user (custom field) before they can move to **IN PROGRESS**
            
        *   During **IN PROGRESS** the user must complete the **Implementation notes** and sign off the **Verification and Validation result** (custom field) before moving to **COMPLETE**
            
*   For users, if they try to transition to a new state but have not completed all the required fields, they are prompted before they can continue. i.e
    
    *   You cannot move to **IN PROGRESS** until the following fields are completed:
        
        *   Identified actions
            
        *   Approved by
            
*   These could be &quot;Entry criteria&quot; for each status, rather than required fields per current status. &nbsp;This would enable work packages to move to statuses like **REJECTED** or **ON HOLD** from any state without needing the field completion of the current state.
    
*   **Entry criteria** would be defined on a per status and per work package type as we have a number of shared statuses that work on vastly different work package form designs and process requirements
    

**Technical notes**

*   <br>
    

**Permissions and visibility considerations**

*   Configuration is only visible to administrators controlling functionality for all users
    

**Translation considerations**

*   _Key terms and phrases in the key languages_ 
    

**Out of scope**

*   <br>
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
