# Feature OP-6342 - Set attributes as required (manadatory) depending on work package status 

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 6 |
| List | TIB 2026 |
| 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 | Yes |
| 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 | Bowling (40324) |

## Estimates and progress

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

## Description

We realize in our working packages that essential fields are left blank. It seems that **topic** and **type** of working pakage are the only obligatory fields for a creation up until version 10.0.2.

Once a package is **accepted** or **in progress** it seems that even standard fields are supposed to be mandatory.  With a (project related) configuration, which could set certain standard fields as obligatory, as _estimated time_ or _time spent,_ our company will gain massive productivity by avoiding unnecessary queries.  Moreover, the information quality of working packages automatically increases. This will finally lead to a higher integration of OpenProject in our company.

A relation between the definition of **required fields** and the **current status** seems to only be logical. Here are just two appeal examples, we frequently face:

1.  Please fill out the _estimated time_ before you put the status from _new_ to _accepted_.
2.  Please fill out the _time_ _spent_ before you put the status from in _progress_ to _revised_.
