# Feature SSI-88 - Create and edit custom field of type hierarchy

Project: Stream Storage Integrations
Status: closed
URL: https://community.openproject.org/work_packages/SSI-88

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 15.1.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| SSI-90 | Add model and data migration | Implementation | closed |  | 15.0.0 |  |
| SSI-91 | Add new custom field type "Hierarchy" | Implementation | closed |  |  |  |
| SSI-92 | Add custom field detail page for hierarchy custom fields | Implementation | closed |  |  |  |
| SSI-93 | Add custom field value page for hierarchy custom fields | Implementation | closed |  |  |  |
| SSI-94 | Enable item creation | Implementation | closed |  |  |  |
| SSI-95 | Enable item deletion | Implementation | closed |  |  |  |
| SSI-96 | Enable item editing | Implementation | closed |  |  |  |
| SSI-97 | Add possibility to descend into a value | Implementation | closed |  | 15.0.0 |  |
| SSI-111 | Item persistence service | Implementation | closed |  | 15.0.0 |  |
| SSI-114 | Delete whole hierarchy when deleting root  | Implementation | closed |  |  |  |
| SSI-116 | Add feature spec covering the hierarchy lifecycle in the admin view | Implementation | closed |  |  |  |

## 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 | Eric Schubert |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** an OpenProject administrator  
**I want to** interact with the custom fields administration&nbsp;  
**so that** I can create new custom fields of type hierarchy or edit existing ones.

**Acceptance criteria**

*   On `/custom_fields/new?type=WorkPackageCustomField` the format dropdown contains the option &quot;Hierarchy&quot;.
    
*   When creating a custom field of type hierarchy we need to be able to set the following options:
    
    *   &quot;Name&quot; - Required, String
        
    *   &quot;Allow multi-select&quot; - Checkbox
        
    *   &quot;Required&quot; - Checkbox
        
    *   &quot;For all projects&quot; - Checkbox
        
    *   &quot;Used as a filter&quot; - Checkbox
        
    *   &quot;Searchable&quot; - Checkbox
        
*   When the user clicks on &quot;Save&quot;, the custom field details view is shown.
    
    *   ⚠️ the current behaviour redirect to custom fields index page. Can we change that for this custom field? -&gt; No, not now
        
*   The custom field details view has two sub pages (tabs)
    
    *   Details
        
        *   The &quot;Details&quot; view shows the following options:
            
            *   &quot;Name&quot; - Required, String
                
            *   &quot;Allow multi-select&quot; - Checkbox
                
            *   &quot;Required&quot; - Checkbox
                
            *   &quot;For all projects&quot; - Checkbox
                
            *   &quot;Used as a filter&quot; - Checkbox
                
            *   &quot;Searchable&quot; - Checkbox
                
    *   Items
        
        *   The &quot;Items&quot; view shows a placeholder for the empty items after creation.
            
        *   The user must be able to create new items.
            
        *   The user must be able to assign a label and a short to a new item.
            
        *   The user is not allowed to create a item with a label ~~or a short~~ that already exists on that level.
            
        *   The user must be able to submerge into a item to create sub-items.
            
        *   The user must be able to delete an item.
            
            *   Deletion of a value deletes all sub-items.
                
        *   The user must be able to edit a item.
            
*   If the user submerged into any item, a breadcrumb with the ancestors must be displayed. The user must be able to go to any of the current ancestors.
    

**Important hints**

*   A deletion eventually is possible as hard or soft delete.
    
    *   The first iteration only supports hard delete.
        
    *   A soft delete marks a value and all descendants as deleted, but does not remove the entity from the database.
        
*   A sorting is planned, hence the data model must support an order of values of the same level.
