-
Bug
-
Resolution: Timed out
-
Low
-
2
-
Minor
-
0
-
Issue Summary
Jira generates incorrect Sprint reports with different issue-status when a completed Jira ticket is moved into an active sprint.
Steps to Reproduce
Let's reproduce it with an example:
| Sprint start and end time | 30/Jun/23 4:40 AM - 14/Jul/23 7:48 AM |
| Jira ticket moved to Done | 7 July 2023 at 04:01 |
| Jira ticket moved to Sprint (already done at this point) | 11 July 2023 at 01:51 |
Expected Results
Sprint report should show the correct status when Jira ticket moved to the sprint(in this case it's Done and remained in Done status)
Actual Results
Per the current design, the sprint report considers that Jira issues should only be added to the sprint before the start of the sprint and in a not-done state.
Since a Jira ticket has moved to Done before it was moved to the sprint. It would be inaccurate to mention it as done in the report for that sprint. Hence, the report shows the status of the issue at the time the sprint started ( It was in backlog and in a not-done state).
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available