Content
View differences
Updated by Kabiru Mwenja 1 day ago
**Summary**
In the work package table, baseline comparison between two past dates shows today'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 "Baseline 1.0" three days ago, in "Baseline 1.0" and "Baseline 1.1" two days ago, and in "Baseline 1.0", "Baseline 1.1" and "Baseline 1.2" today (target version 1.0, then 1.1, then 1.2 at the same times).
2. Open the project's work package table with the columns Target versions and Observed in versions.
3. Baseline, "Between two specific dates": first date three days ago, second date two days ago (both before today's change).
**Actual behavior**
Observed in versions shows today's three values, "Baseline 1.0, Baseline 1.1, ..." with a count of 3, as the state at the second date. Target versions shows "Baseline 1.1" with "Baseline 1.0" struck through, which is the correct state at the second date.
**Expected behavior**
Observed in versions shows the versions as of the second date, "Baseline 1.0, Baseline 1.1", with the baseline value "Baseline 1.0" struck through, consistent with the Target versions column.
**Environment**
dev branch, docker development stack, Chromium.
**Screenshots and attachments**
baseline-between-dates-observed-in-wrong.png (the bug), baseline-yesterday-ok.png (baseline "since yesterday", where both columns are correct, for contrast).
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/925957/content">
In the work package table, baseline comparison between two past dates shows today'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 "Baseline 1.0" three days ago, in "Baseline 1.0" and "Baseline 1.1" two days ago, and in "Baseline 1.0", "Baseline 1.1" and "Baseline 1.2" today (target version 1.0, then 1.1, then 1.2 at the same times).
2. Open the project's work package table with the columns Target versions and Observed in versions.
3. Baseline, "Between two specific dates": first date three days ago, second date two days ago (both before today's change).
**Actual behavior**
Observed in versions shows today's three values, "Baseline 1.0, Baseline 1.1, ..." with a count of 3, as the state at the second date. Target versions shows "Baseline 1.1" with "Baseline 1.0" struck through, which is the correct state at the second date.
**Expected behavior**
Observed in versions shows the versions as of the second date, "Baseline 1.0, Baseline 1.1", with the baseline value "Baseline 1.0" struck through, consistent with the Target versions column.
**Environment**
dev branch, docker development stack, Chromium.
**Screenshots and attachments**
baseline-between-dates-observed-in-wrong.png (the bug), baseline-yesterday-ok.png (baseline "since yesterday", where both columns are correct, for contrast).
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/925957/content">