# Feature SSI-102 - Enable assignment of hierarchy values to work packages

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

## Planning

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

## OPEN POINTS / FEEDBACK

| ID | Subject | Status | Decision |
| --- | --- | --- | --- |
| SSI-120 | Do we need a specific search syntax when searching for shorts? | new |  |

## Use cases

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| SSI-121 | Enable selection of custom fields of type hierarchy in project custom fields and wp type form configuration | Implementation | closed |  | 15.1.0 |  |
| SSI-122 | [API] Add endpoint for fetching the tree | Implementation | closed |  | 15.1.0 |  |
| SSI-123 | [API] Add endpoint for fetching a branch | Implementation | closed |  | 15.1.0 |  |
| SSI-124 | Add drop down selector to the custom field value assignment | Implementation | closed |  | 15.1.0 |  |
| SSI-125 | Enable multi-select on the value assignment | Implementation | rejected |  |  |  |
| SSI-126 | Render full branch of hierarchy item value assignment | Implementation | closed |  | 15.1.0 |  |
| SSI-144 | [Test] Write requests tests for new API endpoints | Implementation | closed |  | 15.1.0 |  |
| SSI-147 | Introduce aggregate for fetching hierarchy items for the API | Implementation | closed |  | 15.1.0 |  |
| SSI-163 | Show short identifier of hierarchy items as assigned value | Feature | rejected |  |  |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| OP-16107 | Bug | i18n for english translation not loading for requests | closed |  | 16.5.0 |  | Administration / Custom fields, Modules and project features / Documents |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| 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** a user  
**I want to** add items from a custom field hierarchy as a value to the work package  
**so that** I can select the desired state for my work package.

**Acceptance criteria**

*   A instance admin must be able to add a custom field of type hierarchy to the form configuration of a work package type.
    
*   A project admin must be able to activate a custom field of type hierarchy inside a project.
    
*   A user must be able to select one (no multi-select) or many (with multi-select) items from the hierarchy to assign them to the work package.
    

**Trivia**

*   Focus is still on work package custom fields.
    
*   Work package view is angular
    
    *   we use the ng-select component first (drill down selector is not ready yet)
        
    *   we need at least some api access to fetch the needed data
        
*   Does rendering the custom field value impacts heavily the load of the work package? Investigate!
