Custom Fields MVC1: Basic Fields
# 📊 **Project Dashboard**
*Date: `2025-04-04`*
---
## 🗂️ **Epic Overview**
- **Epic Name:** [Custom Fields MVC1: Basic Fields](https://gitlab.com/groups/gitlab-org/-/epics/14904)
- **Total Key Features in Epic:** `7`
- **Completed Features:** `4`
- 🟢 **Overall Project Status: Green**
---
## 📅 **Project Timeline**
```mermaid
%% Gantt chart showing the project timeline with milestones
gantt
title Project Timeline
dateFormat YYYY-MM-DD
section Features
[Custom Fields] Archive/Unarchive (or delete) a custom field :f1, 2025-01-11, 2025-03-14
[Custom Fields] Interact with custom fields in the work item detail view :f2, 2025-01-11, 2025-04-11
[Custom Fields] Interact with custom fields in the work item creation flow :f3, 2025-02-15, 2025-04-11
[Custom Fields] Filter by select custom fields :f4, 2025-01-11, 2025-04-11
[Custom Fields] Limit number of fields per namespace :f5, 2025-01-11, 2025-02-14
[Custom Fields] Configure custom fields at the root namespace level :f6, 2024-09-14, 2025-03-14
[Custom Fields] Cascade work item configuration to all child namespaces :f7, 2024-12-13, 2025-01-10
section Key Points
Backend Complete :milestone, m1, 2025-03-14, 0d
Development Complete:milestone, m2, 2025-04-11, 0d
End of Quarter :milestone, m3, 2025-04-30, 0d
```
---
## 🎯 **Targets**
| **Target** | **Date** | **Status** |
| ---------------------------- | ---------- | ---------- |
| Backend Integration Complete | 2025-03-14 | On Track |
| Development Phase Complete | 2025-04-11 | Upcoming |
| Feature Flag Defaulted to On | 2025-04-11 | Upcoming |
| End of Quarter | 2025-04-30 | Upcoming |
---
## 🚀 **Key Features**
| **Feature** | **Progress** | **Work Completed/Total** |
| ---------------------------------------------------- | ------------ | ------------------------ |
| https://gitlab.com/gitlab-org/gitlab/issues/479571+s | 90% | 9/10 |
| https://gitlab.com/gitlab-org/gitlab/issues/479572+s | 50% | 2/4 |
| https://gitlab.com/gitlab-org/gitlab/issues/479573+s | 63% | 5/8 |
| https://gitlab.com/gitlab-org/gitlab/issues/504677+s | 100% | 2/2 |
| https://gitlab.com/gitlab-org/gitlab/issues/479569+s | 100% | 4/4 |
| https://gitlab.com/groups/gitlab-org/-/epics/15946+s | 100% | 22/22 |
| https://gitlab.com/gitlab-org/gitlab/issues/479574+s | 100% | 0/0 |
---
## Use Cases
* _As a `Maintainer+`, I can create a custom field in a root namespace._
* _As a `Guest+`, I can enter values for custom fields when creating a work item._
* _As a `Reporter+`, I can update the the values for custom fields on work items._
## Work Items scope for the custom fields widget
https://gitlab.com/groups/gitlab-org/-/epics/235#work-item-type-scopes
## UX
https://gitlab.com/gitlab-org/gitlab/-/issues/461471+
## Basic Fields
- Select list
- Number
- String
## Priority of vertical slices (issues)
The order of the issues in the child items widget reflects the general stack-ranked order for implementation. Please chat with PM/UX to propose a reorder of the implementation path.
## Key Features:
:white_check_mark: Verified by PM
* Field Types:
* :white_check_mark: Text
* :white_check_mark: Number
* :white_check_mark: Single-select dropdown
* :white_check_mark: Multi-select dropwn
* Field Management:
* :white_check_mark: Create/Edit fields at the root group level
* :white_check_mark: Map fields to work item types
* :white_check_mark: Archive/unarchive custom fields (no delete for MVC1)
* :white_check_mark: Application limits
* :white_check_mark: General error handling / sad paths
* :white_check_mark: Handle moving namespaces
* Work Item Integration:
* :white_check_mark: View/Edit custom fields/values within a work item
* :white_check_mark: Interact w/ custom fields/values when creating a work item
* :white_check_mark: Filter customer fields in boards and lists (select list only)
* Risk: https://gitlab.com/groups/gitlab-org/-/epics/9937+
Can potentially defer:
* Notifications and webhooks
* Custom fields from root group should apply to all work items types in self and child namespaces
### Release notes
With this release, you can configure text, number, single-select, and multi-select custom fields for issues, epics, tasks, objectives, and key results. While labels have been the primary way to categorize work items up to this point, custom fields provide a more user-friendly approach for adding structured metadata to your planning artifacts. Custom fields are configured in your top-level group and cascade to all subgroups and projects. You can map fields to one or more work item types and filter by custom field values in the issues and epics lists.
https://docs.gitlab.com/user/work_items/custom_fields/
epic