# Feature OP-19713 - OP Administration: Show custom field name in delete confirmation

Project: OpenProject
Status: tested
URL: https://community.openproject.org/work_packages/OP-19713

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0, Passion time |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| 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 | Administration / Custom fields, Frontend components and Primer design system |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan | Community (COM) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | Max Mulatz |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

### **Description**

In _Administration &gt; Custom fields_, deleting a custom field already triggers a confirmation pop-up asking the administrator to confirm the deletion.  
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/922583/content">

This is helpful, but the confirmation dialog **does not clearly repeat** which exact custom field is about to be deleted.

### **Feature request**

Please include the name of the custom field in the delete confirmation pop-up.

### **Expected behavior**

When an administrator deletes a custom field

*   A `Primer::OpenProject::DangerDialog` appears
    
*   &nbsp;The dialog title for a screen reader should be: &quot;Delete custom field %{name}&quot;
    
*   The dialog heading should say: &quot;Do you want to delete the custom field %{name}?&quot;
    

**Additional context:**  
This would help prevent accidental deletion, especially in instances with many custom fields or similarly named fields.
