# Feature SPPM-336 - Support multiple selection in weighted lists

Project: Stream Project Portfolio Management
Status: merged
URL: https://community.openproject.org/work_packages/SPPM-336

## Planning

| Attribute | Value |
| --- | --- |
| Date | 2026-11-05 |
| Priority | Medium |
| Target versions | 18.0.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| SPPM-337 | Improve feedback for misuse of multi-select lists in calculated values | Implementation | review approved |  | 18.0.0 |  |
| SPPM-339 | Update dentaku gem | Implementation | new |  |  |  |

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Administration / Custom fields |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan | Enterprise / Premium (PRE) |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Jens Ulferts |
| Product manager | Felicia Mundhenke |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** an administrator configuring calculated values  
**I want to** allow multiple selections in weighted lists and define how their values are processed using the available scoring operators  
**so that** multiple applicable options can contribute to a calculated result and be used in further calculations.

Example:

*   An organization can use this to prioritize projects. Using the functionality, a weighted list can be configured listing categories of reasons for why a project should be implemented. E.g. "Reduction of bureaucracy", "Compliance", "Strategic goal". Each could get a certain numerical value. A user evaluating the project selects one or multiple of the options, e.g "Reduction of bureaucracy", "Strategic goal", and the sum of the values of both is then input for the calculated overall value.
    

**Acceptance criteria**

*   Weighted list project attributes can be configured to allow multiple selections.
    
    *   Displaying the field in the project overview and selecting changed values is supported
        
    *   Using multi fields in the project list as filters and columns is supported.
        
    *   The projects API displays such attributes for configured projects and allows setting them.
        
    *   Each option can have its own configured weight / score. This is existing functionality
        
    *   Weighted item project attributes not having multiple sections active continue to work as before.
        
*   Calculated value project attributes:
    
    *   can include weighted item lists with multiple values activated
        
    *   get two additional functions:
        
        *    `MUL`
            
        *   `COUNT`
            
    *   have the functions `MIN` , `MAX`, `SUM`, `AVG`, `COUNT` und `MUL` grouped into a new section 'List functions'
        
    *   calculate successfully with a weighted item list having multiple values in the above operators, e.g. `SUM("some multi field")`
        
    *   calculate successfully with a weighted item list having multiple values as well as single fields, e.g. `MUL("some multi field", 42, "some single field")`
        
    *   calculate successfully with a weighted item list having only single values same as before.
        
    *   fail to calculate with a weighted item list having multiple values in operations that require a single value, e.g. `5 + "some multi field" - 4`. Ideally, this is spotted when the formula is inserted. This is not a must. It is acceptable to display an error on the project overview page on calculation.
        
    *   are recalculated if they contain a weighted item list as a variable for which the "multi" selection property is toggled.
        

**Technical notes**

*   Currently, weighted lists only support single selection.
    
*   The implementation should enable multiple selected values to be used with the existing scoring operators and formula logic.
    
*   The functionality should extend the existing weighted list and calculated values logic rather than introduce a separate calculation mechanism.
    

**Permissions and visibility considerations**

*   The functionality is available to users who have permission to configure weighted lists / calculated values.
    
*   No changes to existing permissions or visibility of fields are required.
    

**Translation considerations**

*   Multiple selection
    
*   Weighted list
    
*   Weight / score
    
*   Scoring operator
    
*   Calculated value
    

**Out of scope**

*   Changes to the existing single-selection behavior of weighted lists.
    
*   Introduction of new scoring operators specifically for weighted multi-select lists.
    
*   Changes to other multi-select field types.
    
    <br>
    

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