# Feature COMMS-839 - Introduce target versions replacing version

Project: Stream Communicator
Status: closed
URL: https://community.openproject.org/work_packages/COMMS-839

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.8.0 |
| Sprint | Sprint 10 |
| Backlog bucket |  |
| 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 |
| --- | --- | --- | --- | --- | --- | --- |
| COMMS-840 | Retain version column in WP list view after conversion to Target Versions | Implementation | closed |  |  |  |
| COMMS-841 | Adjust the defaults for types form configuration - version/target_versions | Implementation | closed |  |  |  |
| COMMS-842 | Adjust version boards behaviour to handle multiple versions | Implementation | rejected |  |  |  |
| COMMS-843 | Make new installations default to multiple versions enabled | Implementation | closed |  |  |  |
| COMMS-844 | Implement the admin "switch" to enable multiple versions | Implementation | closed |  | 17.8.0 |  |
| COMMS-851 | Adjust boards to read/write from target_versions | Implementation | rejected |  |  |  |
| COMMS-876 | Adjust CKEditor version macros: single-line/multi-line layout argument for attribute value macros | Feature | closed |  | 17.8.0 |  |
| COMMS-884 | Adjust filters, groups and sorting of multiple versions | Implementation | closed |  |  |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| COMMS-985 | Bug | Target versions shows old and new version if version was changed before Target versions are enabled on the instance | closed |  | 17.8.0 |  |  |
| COMMS-986 | Bug | Drag and drop of work packages in a grouped by query doesn't work with Target versions | closed |  | 17.8.0 |  |  |
| COMMS-956 | Bug | Gantt charts PDF export with target versions outputs object ids | closed |  | 17.8.0 |  |  |
| COMMS-955 | Bug | Work package lists PDF export with target versions outputs object ids | closed |  | 17.8.0 |  |  |
| COMMS-954 | Bug | Both "Target version" and "Version" filters are present when target versions is enabled | closed |  | 17.8.0 |  |  |
| COMMS-951 | Documentation | Introduce target versions replacing version | closed | Maya Berdygylyjova | 17.8.0 |  |  |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/YjZZs8xOYcesF4JgDQWh1C/Target-versions-and-categories?node-id=0-1 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer | Parimal Satyal |
| 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** be able to assign multiple versions to a work package  
**so that** i can better organise work

**As** an admin of an existing instance  
**I want to** be able decide when to enable multiple versions on work packages  
**so that** I can handle integrations

**Acceptance criteria**

*   There is a new admin settings page: Administration → Work packages → Versions and categories
    
*   On this page, admins are informed of upcoming changes to the &#x27;Version&#x27; and &#x27;Category&#x27; fields and have an opportunity to manually enable multiple values for both before the migration is automatically applied in a future version.
    
*   The changes happen in three stages:
    
    *   Possible to manually enable multiple values only for &#x27;Version&#x27;&nbsp;
        
    *   &#x27;Target versions&#x27; already multi-value but Category can now be manually migrated
        
    *   Neither field has been migrated but possible to manually enable multiple values for both
        
    *   Automatic migration complete
        
*   On the top of the page is a warning banner:
    
    *   Variant: Warning
        
    *   Text: &quot;There are important upcoming changes to versions and categories. Please carefully review the following settings.&quot;
        
    *   Action: &quot;More information&quot; (invisible button)
        
        *   This leads to documentation to help admins understand the changes and how to update API clients.
            
*   There are two sections marked with Subheads:
    
    *   Target versions
        
    *   Categories
        
*   The contents of these sections depends on which stage of the migration the admin users finds herself. There are four cases possible as described below.
    

**Case 1: Possible to manually enable multiple values only for &#x27;Version&#x27;**

*   Under &#x27;Target versions&#x27;, there are two [Inset Box](https://qa.openproject-edge.com/lookbook/pages/components/inset_box) sections:
    
    *   &quot;Planned changes in a future release&quot; give users two pieces of information, with an `info` preceding each:
        
        *   &quot;The “Version” field will be renamed “Target versions”.&quot;
            
        *   &quot;This field is currently single-value. It will both be converted to allow multiple values.&quot;
            
    *   &quot;Action required&quot; gives lets admins enable multiple values manually:
        
        *   Information with icon `tools`, &quot;You can choose to manually run the conversion to enable multiple values before this automatic migration happens.
            
        *   Button (secondary): &quot;Enable multiple values&quot;
            
*   Under &#x27;Categories&#x27;, there is one [Inset Box](https://qa.openproject-edge.com/lookbook/pages/components/inset_box) section titled &quot;Planned changes in a future release&quot;
    
    *   There are two pieces of information, with an `info` icon preceding each:
        
        *   &quot;The “Category” field will be renamed “Target versions”.
            
        *   &quot;This field is currently single-value. It will both be converted to allow multiple values.&quot;
            
    *   This is one information with an `hourglass` icon preceding it:
        
        *   &quot;You will be able to choose to enable multiple values before this automatic conversion happens.&quot;
            
    *   There are no available actions.
        
*   Clicking on &quot;Enable multiple values&quot;, displays a Danger Confirmation dialog (see Figma for content).
    
    *   Once confirmed, both Subhead sections under &#x27;Target versions&#x27; is replaced by a single Inset Box with a loading message:
        
        *   A small spinner
            
        *   Text (medium bold): &quot;Enabling multiple versions&quot;
            
    *   Once the migration is complete:
        
        *   The Subhead section is replaced with a title: &quot;Recent changes&quot;
            
        *   With two pieces of information with a green (success) `check` icons:
            
            *   &quot;The “Version” field has now been renamed “Target versions”.
                
            *   The “Target versions” field now allows multiple values.
                
        *   A piece of information with an `info` icon:
            
            *   &quot;For more information on this change and how to update API clients, please refer to [our documentation](https://community.openproject.org/#).&quot;
                
            *   The link leads to documentation to help admins understand the changes and how to update API clients.
                

**Case 2: &#x27;Target versions&#x27; already multi-value but Category can now be manually migrated**

*   Similar to case 1, except:
    
    *   The &#x27;Target versions&#x27; section has the same state as when the migration is complete
        
    *   The &#x27;Categories&#x27; section has two [Inset Box](https://qa.openproject-edge.com/lookbook/pages/components/inset_box) sections:
        
        *   &quot;Planned changes in a future release&quot; give users two pieces of information, with an `info` preceding each:
            
            *   &quot;The “Category” field will be renamed “Categories”.&quot;
                
            *   &quot;This field is currently single-value. It will both be converted to allow multiple values.&quot;
                
        *   &quot;Action required&quot; gives lets admins enable multiple values manually:
            
            *   Information with icon `tools`, &quot;You can choose to manually run the conversion to enable multiple values before this automatic migration happens.
                
            *   Button (secondary): &quot;Enable multiple values&quot;
                
        *   Clicking on &quot;Enable multiple values&quot;, displays a Danger Confirmation dialog (see Figma for content).
            
            *   Once confirmed, both Subhead sections under &#x27;Categries&#x27; is replaced by a single Inset Box with a loading message:
                
                *   A small spinner
                    
                *   Text (medium bold): &quot;Enabling multiple versions&quot;
                    
            *   Once the migration is complete,
                
                *   The whole page now only has one Inset Box with title &quot;Recent changes&quot;
                    
                    *   There are two pieces of information with a green (success) `check` icons:
                        
                        *   &quot;The “Version” field has now been renamed “Target versions” and allows multiple values&quot;.
                            
                        *   &quot;The “Category” field has now been renamed “Categories” and allows multiple values.&quot;
                            
                    *   A piece of information with an `info` icon:
                        
                        *   &quot;For more information on this change and how to update API clients, please refer to [our documentation](https://community.openproject.org/#).&quot;
                            
                        *   The link leads to documentation to help admins understand the changes and how to update API clients.
                            

**Case 3: Neither field has been migrated but possible to manually enable multiple values for both**

*   There are no Subheads.
    
*   There are simply two [Inset Box](https://qa.openproject-edge.com/lookbook/pages/components/inset_box) sections:
    
    *   &quot;Planned changes in a future release&quot; give users three pieces of information, with an `info` preceding each:
        
        *   &quot;The “Version” field will be renamed “Target versions”.&quot;
            
        *   &quot;The “Category” field will be renamed “Categories”.&quot;
            
        *   &quot;Both of these fields are currently single-value. They will both be converted to allow multiple values in a future release.&quot;
            
    *   &quot;Action required&quot; gives lets admins enable multiple values manually:
        
        *   Information with icon `tools`, &quot;You can choose to manually run the conversion to enable multiple values before this automatic migration happens.
            
        *   Button (primary): &quot;Enable multiple values&quot;
            
    *   Clicking on &quot;Enable multiple values&quot;, displays a Danger Confirmation dialog (see Figma for content).
        
        *   Once confirmed, both boxes are replaced by a single Inset Box with a loading message:
            
            *   A small spinner
                
            *   Text (medium bold): &quot;Enabling multiple versions&quot;
                
        *   Once the migration is complete,
            
            *   The whole page now only has one Inset Box with title &quot;Recent changes&quot;
                
                *   There are two pieces of information with a green (success) `check` icons:
                    
                    *   &quot;The “Version” field has now been renamed “Target versions” and allows multiple values&quot;.
                        
                    *   &quot;The “Category” field has now been renamed “Categories” and allows multiple values.&quot;
                        
                *   A piece of information with an `info` icon:
                    
                    *   &quot;For more information on this change and how to update API clients, please refer to [our documentation](https://community.openproject.org/#).&quot;
                        
                    *   The link leads to documentation to help admins understand the changes and how to update API clients.
                        

**Automatic migration complete**

*   The whole page now only has one Inset Box with title &quot;Recent changes&quot;
    
    *   There are two pieces of information with a green (success) `check` icons:
        
        *   &quot;The “Version” field has now been renamed “Target versions” and allows multiple values&quot;.
            
        *   &quot;The “Category” field has now been renamed “Categories” and allows multiple values.&quot;
            
    *   A piece of information with an `info` icon:
        
        *   &quot;For more information on this change and how to update API clients, please refer to [our documentation](https://community.openproject.org/#).&quot;
            
        *   The link leads to documentation to help admins understand the changes and how to update API clients.
            

**Other specs**

*   Admins can successfully enable multiple versions on work packages (cannot disable, though)
    
    *   The migration is one-way
        
*   Users are able to edit target versions in work packages details form
    
*   Users are able to edit target versions in work packages list view
    
*   Users can use version boards with multiple versions
    
    *   same work package can be seen in multiple columns
        
    *   dragging a work package from a column to another appropriately removes the source version and includes the target version to the work package
        
*   Setting up a new instance of OpenProject comes with multiple versions enabled by default
    

**Technical notes**

*   ...
    

**Out of scope**

*   <br>
