# Epic FND-27 - Introduce 'target versions' so we can separate 'Observed in versions' from 'Release versions'

Project: Stream workspace foundations
Status: closed
URL: https://community.openproject.org/work_packages/FND-27

## Detailed specification

### Motivation and background information

Software companies want to communicate that a certain feature or bug will be released in multiple versions (e.g. latest version, but also in a LTS version). Bugs can be observed in multiple versions, too.

**Release Version/s** = planning & release tracking (adds issue to a release)

  - The version(s) in which the issue's fix will be released. Adding a version here **adds the issue to that release**. Drives the Version Report and release tracking.

**Observed in Version/s** = impact reporting (no release association)

  - The version(s) of the product that the issue was observed in (e.g., "this bug exists in v1.0 and v1.1"). Does **not** add the issue to the release - it's for tracking impact only.

### Acceptance criteria

*   There are two new version fields
    
    *   Target versions
        
        *   Current field "version" can be renamed / replaced with "target version"
            
    *   Observed in versions
        
*   They both use the same set of versions, there are no separate version sets
    
*   Both fields are multi-select
    
*   default visibility in work packages
    
    *   release version visible per default in
        
        *   epic
            
        *   feature
            
        *   bug
            
        *   user story
            
    *   observed in version visible per default in
        
        *   bug
            
*   \[open: some of the changes below are only logical for _Target versions_; eg. "release date" doesn't make sense for _Observed in version_\] ~~Attributes for "release version" and "observed in version"~~
    
    *   ~~Name~~
        
    *   ~~Description~~
        
    *   ~~Status~~
        
        *   ~~unreleased (should replace the status "open")~~
            
        *   ~~released (should replace the status "closed")~~
            
        *   ~~archived (should replace the status "locked")~~
            
    *   ~~Start date~~
        
    *   ~~Release date (should replace "Finish date")~~
        
    *   ~~Sharing~~
        
        *   ~~With subprojects~~
            
        *   ~~With project hierarchy~~
            
        *   ~~With all projects~~
            
    *   ~~Wiki page and column in backlog can be removed~~
        
*   Is available in
    
    *   API
        
    *   Filter
        
    *   Grouping
        
    *   List
        
    *   Work package details view
        
    *   Roadmap

### Out of scope

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

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2026 Q3 |
| Date |  |
| Votes |  |
| List | RM Jira exit, RM Jira admin, RM Jira Migrator |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

| ID | Type | Subject | Status | Assignee | Target versions | Project | Priority | Spent time |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| COMMS-857 | Implementation | Introduce new target_versions field on WorkPackage API | closed |  | 17.7.0 | Stream Communicator | Medium |  |
| COMMS-839 | Feature | Introduce target versions replacing version | closed |  | 17.8.0 | Stream Communicator | Medium |  |
| COMMS-845 | Feature | Make target_versions the canonical data source for all subsystems in OpenProject | closed |  | 17.8.0 | Stream Communicator | Medium |  |
| COMMS-859 | Feature | Introduce observed in versions | closed |  | 17.9.0 | Stream Communicator | Medium |  |
| FND-178 | Open Point | Cost reports over-count totals when grouping or filtering by a multi-value attribute | needs clarification |  |  | Stream workspace foundations | Medium |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Module |
| --- | --- | --- | --- | --- | --- | --- |
| COMMS-997 | Bug | "Only changes" work packages activity filter hides target and observed-in version changes | closed |  | 17.9.0 | Modules and project features / Comments and activity |
| COMMS-906 | Task | Technical documentation for migration | rejected |  |  |  |
| FND-250 | Task | Create a task to migrate "Bug found in version" field to "Observed in Versions" in community | in review |  |  |  |
| FND-178 | Open Point | Cost reports over-count totals when grouping or filtering by a multi-value attribute | needs clarification |  |  |  |

## Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Roadmap |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Wieland Lindenthal |
| Accountable | Wieland Lindenthal |
| Product manager | Wieland Lindenthal |
| Designer |  |
| Developers | OP Dev Comms Team |
| Requested by |  |
| Interest by | Black (37919), Home (224196000003952096) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | 60d 0h · Σ 60d 0h |

## Description

**As an** OpenProject user

**I want to** import issues from Jira

**I need** two different version fields: affects version and fix version

**And** in both fields I should be able to add multiple values.