I'm trying to understand how this can be in any way consistent.
Task A is in Sprint A
work is logged on Task A during Sprint A
last day of Sprint A, Task A is moved to Sprint B
Task A no longer appears in the Sprint Report for Sprint A at all
I know that some tasks appear as removed from sprint but I just cannot imagine why this one doesn't. There are a number of them and there's no discernible pattern. Some pictures:
This task was in the sprint when the sprint was started and had work logged on it during the sprint:
Today, I removed it from the sprint and pushed it to next sprint. It's completely gone from the sprint report:
And the bottom of the list:
As you can see, one random task appears as "Issue Removed from Sprint" but not 8421 (and many others). Any idea why?
After talking to atlassian, it seems like this is a known bug. I guess this issue doesn't have more traction since a lot of people don't even notice it happens. However, it does hurt the accuracy of the reports as well as people's trust in the reports if they ever notice it happens.
Repro steps are:
1. Create a task and assign it to a sprint (Sprint A)
1a. Log some work on the task
2. Close the sprint with the task inside it (and incomplete)
=> the task will have Completed Sprints: Sprint A
3. Assign the task to another sprint (Sprint B)
3a. Log some more work on the task
4. Remove the task from the sprint
The task completely disappears from the sprint report / burndown report for Sprint B.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG