Required Fields (including Custom Fields)

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Issues

• https://gitlab.com/gitlab-org/gitlab-ee/issues/1906 Custom fields in issues
• https://gitlab.com/gitlab-org/gitlab-ee/issues/2493 Custom fields with required validation
• https://gitlab.com/gitlab-org/gitlab-ee/issues/2503 Custom fields in groups
• https://gitlab.com/gitlab-org/gitlab-ee/issues/2504 Custom fields with enumerated field type

Description

• Configurable required validation for fields, so that when you create a new issue, you have to enter those fields, if toggled on.
• We are moving away from the concept of "editing an issue". Instead, you should be able to change attributes to an issue independently of other attributes easily in the UI. So in this context, when you create a new issue (and required validation is turned on for a custom field), you have to fill out that field. But when you go to an existing issue, you can change anything independently. But if you change a custom field with required validation, you cannot change it to be blank. This wouldn't apply to legacy issues or fields that you subsequently made required.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.