-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
9.12.10
-
9.12
-
2
-
Severity 2 - Major
-
10
-
Issue Summary
The Plan Target end date is not set correctly when the issue is associated with multiple Sprints
Steps to Reproduce
- In the Plan configuration > Scheduling > Dates > tick "Use sprint dates when issues don't have start and end dates"
- Create issue TPA-24 and add it to active Sprint 1
- The Target start date is 17 Nov 2024 and the Target end date is 22 Nov 2024. (Same as Sprint 1)
- Complete Sprint 1 and move TPA-24 to Sprint 2
- The Target start date is 17 Nov 2024 and the Target end date is 28 Nov 2024. (Target end is same as Sprint 2)
- Complete Sprint 2 and move TPA-24 to Sprint 3 on 19 Nov
- The Target start date is 17 Nov 2024 and the Target end date is 30 Nov 2024. (Target end is same as Sprint 3)
- Now start Sprint 3, and complete TPA-24 on 21 Nov.
- The Target start date is 17 Nov 2024 and the Target end date is 18 Nov 2024.
Expected Results
When the issue TPA-24 is closed, we expect the Target end date to remain the End date of Sprint 3.
Actual Results
When the issue TPA-24 is closed, the Target end date was updated to the Sprint 2 completed date.
In the Plan, the Target end date is showing 1 day before the Sprint 2 completed date, it is relevant to the known bug: JSWSERVER-25046: Target End showing -1 day for active sprints on Plans
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available
- relates to
-
-
- Gathering Impact
-
- links to
- mentioned in
-
Page Failed to load
Hi c2fb5f6b04a3 Do you have a running env with this bug?