# Feature COMMS-859 - Introduce observed in versions

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.9.0 |
| Sprint | Sprint 15 |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

| ID | Subject | Status | Decision |
| --- | --- | --- | --- |
| COMMS-994 | Should we attempt to include the field Observed In Versions on bug types for existing projects? | decided | Do not include field + make documentation + release notes + rake task to facilitate migration |
| COMMS-995 | Should observed_in_versions allow assigning closed versions? | decided | yes, closed versions need to be selectable |

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| COMMS-887 | Introduce observed_in_versions to the WorkPackage API | Implementation | closed |  | 17.9.0 |  |
| COMMS-964 | Include observed in versions on Work Package list view & details form | Implementation | closed |  | 17.9.0 |  |
| COMMS-965 | Make observed in versions default for bug types (seeder adjustment) | Implementation | closed |  | 17.9.0 |  |
| COMMS-966 | Adjust journals to represent observed in versions | Implementation | closed |  | 17.9.0 |  |
| COMMS-967 | Adjust base contract and service validations for observed in versions | Implementation | closed |  | 17.9.0 |  |
| COMMS-968 | Adjust copying projects and work packages to include observed in versions | Implementation | closed |  | 17.9.0 |  |
| COMMS-969 | Adjust filters, grouping and sorting for observed in versions | Implementation | closed |  | 17.9.0 |  |
| COMMS-970 | Adjust PDF/CSV/Gantt exports with observed in versions | Implementation | closed |  | 17.9.0 |  |
| COMMS-971 | Support `observed_in_versions` in MCP work package filtering | Implementation | rejected | Tom Hykel | 17.9.0 |  |
| COMMS-972 | Subject auto-generation (TokenPropertyMapper) support | Implementation | closed |  | 17.9.0 |  |
| COMMS-973 | Adapt the cache checksum mechanism for observed_in_versions | Implementation | closed |  | 17.9.0 |  |
| COMMS-974 | Adjust bulk edit to support observed in versions | Implementation | closed |  | 17.9.0 |  |
| COMMS-975 | Adjust move work package to support observed in versions | Implementation | closed |  | 17.9.0 |  |
| COMMS-977 | Adjust Baseline to support observed in versions | Implementation | closed |  | 17.9.0 |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| COMMS-999 | Code maintenance | XLS export does not eager-load Observed in Versions | closed |  | 17.9.0 |  |  |
| COMMS-976 | Task | Investigate BIM - check if there's any necessary changes | closed | Tom Hykel |  |  |  |

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

## Estimates and progress

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

## Description

**As** a member working on a project  
**I want to** record the versions in which a work package can be observed in (e.g. bug tickets)  
**so that** I can tell which versions that work package affects

**Acceptance criteria**

*   Work packages have a new multi value field called Observed In Versions
    
*   Observed in versions field allow the same set of versions as Target Versions + closed versions for a given work package
    
*   The field is enabled by default for Bug types
    
*   The field can be enabled in any type
    

**Technical notes**

*   This feature uses the same table as Target Versions. The data model is already setup in OpenProject
    
*   Most subsystems do not need to be adapted (if any), as they rely on Target Versions instead
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
    *   Anyone that can view work packages
        
    *   Can only be edited when the user has the ability to assign versions (assign\_versions permission)
        

**Out of scope**

*   ?
    

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