# Feature OP-20434 - Add a user setting that inline edit fields only get edited when double clicking

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

## 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 |  |
| 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 | Klaus Zanders |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a user  
**I want to** define that I only enter the edit mode for inline editable fields by double clicking  
**so that** I do not accidentally edit fields when clicking around (especially when selecting text in the work package description)

**Acceptance criteria**

*   Add a new setting **Require double click to edit fields** in Account Settings -&gt; Interface, default for this is **off**
    
*   When the setting is enabled, clicking on an in-place editable field does not open the editor anymore (especially noticable on the Work Package description field), but it requires double clicking
    
*   Users using keyboard navigation are not affected, single enter/space still allows them to enter edit mode
    

**Technical notes**

*   <br>
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
*   _When is it not visible?_
    

**Translation considerations**

*   _Key terms and phrases in the key languages_&nbsp;
    

**Out of scope**

*   <br>
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
