# Bug COMMS-1068 - Observed-in versions keep current values when a baseline request ends at a historic timestamp

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

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module | Modules and project features / Work packages |
| Target versions | 18.0.0 |
| Observed in versions | 17.9.0, 17.9.1, 17.9.2, 17.9.3 |
| Sprint |  |
| Backlog bucket |  |
| Bug found in version (deprecated) |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

**Summary**

In the work package table, baseline comparison between two past dates shows today&#x27;s observed-in versions instead of the versions the work package had at the second date. Every other column, including Target versions, shows the state at that date.

**Steps to reproduce**

1.  A work package whose observed-in versions changed over time, for example observed in &quot;Baseline 1.0&quot; three days ago, in &quot;Baseline 1.0&quot; and &quot;Baseline 1.1&quot; two days ago, and in &quot;Baseline 1.0&quot;, &quot;Baseline 1.1&quot; and &quot;Baseline 1.2&quot; today (target version 1.0, then 1.1, then 1.2 at the same times).
    
2.  Open the project&#x27;s work package table with the columns Target versions and Observed in versions.
    
3.  Baseline, &quot;Between two specific dates&quot;: first date three days ago, second date two days ago (both before today&#x27;s change).
    

**Actual behavior**

Observed in versions shows today&#x27;s three values, &quot;Baseline 1.0, Baseline 1.1, ...&quot; with a count of 3, as the state at the second date. Target versions shows &quot;Baseline 1.1&quot; with &quot;Baseline 1.0&quot; struck through, which is the correct state at the second date.

**Expected behavior**

Observed in versions shows the versions as of the second date, &quot;Baseline 1.0, Baseline 1.1&quot;, with the baseline value &quot;Baseline 1.0&quot; struck through, consistent with the Target versions column.

**Screenshots and attachments**

baseline-between-dates-observed-in-wrong.png (the bug), baseline-yesterday-ok.png (baseline &quot;since yesterday&quot;, where both columns are correct, for contrast).

<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/925957/content">
