# Feature OP-4438 - Custom fields of type "Link/URL"

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-4438

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 14.1.0 |
| Sprint | 14.1.0 |
| Backlog bucket |  |
| Votes | 15 |
| 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 | Yes |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Oliver Günther |
| Product manager |  |
| Feature Lead |  |
| Developers | Oliver Günther |
| Designer | Marc Alcobé |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** an OpenProject user  
**I want** to be able to add a link to a custom field type text  
**in order to** quickly link to a page.

**Acceptance criteria**

*   New custom field type &quot;Link (URL)&quot; in the administration settings.
    
    *   The Link type has an optional attribute &quot;Regexp&quot; that allows to restrict what URLs/schemes/etc. can be entered with a regex
        
    *   The Link type can be marked as required
        
    *   The Link type can have a default value
        
    *   The Link type can be marked for all projects (possibly bound to change with the changes in the project selection)
        
*   In the work package screen
    
    *   When empty, the default placeholder is shown
        
    *   When present, the URL is shown and an edit icon beside it. The icon is shown always (not only on hover)
        
    *   Entering a parseable link will be accepted
        
        *   additional regex validation will take place if configured
            
        *   open: How flexible do we want URLs to be parsed. e.g., is \`mailto:foo@example.com\` &nbsp;valid? It is a valid URI.
            
        *   open: auto-parse URLs like `community.openproject.org`
            
    *   Entering an invalid or unparseable URL
        
        *   will result in the field being marked as error
            
        *   a toast validation message is shown &quot;&lt;field name&gt; is not a valid URL.&quot;
            
    *   Entering a URL that does not match the regexp
        
        *   will result in the field being marked as error
            
        *   a toast validation message is shown &quot;&lt;field name&gt; is invalid.&quot; consistent with other regex custom field validation messages
            
*   Clicking on the link opens the target
    
    *   If the link is on the same host, in the same window
        
    *   If the link is on another host, in a new window (compliance behavior for external links, to be later changed to &quot;external link warning&quot;)
        
*   Activities / Journal changes for the links
    
    *   Links are rendered as plain text
        

**Out of scope**

*   Primerization of custom field form or other fields
    

  

**Visuals and Figma**

https://www.figma.com/file/oTMDTvcwrx35qExTkkSKBn/Custom-fields?type=design&amp;node-id=624-13975&amp;mode=design
