# Feature OP-8115 - Option to set non-custom workpackage fields as required (mandatory)

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 8 |
| 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 | Modules and project features / Work packages |
| 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 |  |

## Estimates and progress

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

## Description

It would be great to have an option to mark certain non-custom fields of workpackages as mandatory. This would reduce time needed for projectsadmins or other users to get all information set which were forgotten by the user during ticket creation

Of course this option has to be applied on project basis.

This option is provided for custom fields, but this does not help in a standard workflow where no custom fields are used.

Similar to:

https://community.openproject.com/projects/openproject/work\_packages/15225/activity
