Refreshing sprint taskboard view shows all stories instead of current
Hi all,
When refreshing the taskboard view of the current sprint backlog, I can see that *all* stories and tasks are displayed, not only the ones planned for that sprint.
Currently we use the standard SCRUM template and plan our sprints with it.
The current plan (sprint backlog) contains (of course ;-)) the current stories and tasks.
When I open the plan, as default the Work Breakdown view is selected. Then I switch to the “Taskboard” view. All stories and tasks are displayed correctly.
When I click on “refresh” (the RTC refresh, not the browser’s refresh), the display shows *all* stories and related tasks, not only the ones planned for that sprint.
That stays even when I use the browser’s “refresh”.
Could reproduce it with both IE and Firefox and 2 different users.
Anyone having the same experience? Or is this a configuration issue?
Regards
Heike
When refreshing the taskboard view of the current sprint backlog, I can see that *all* stories and tasks are displayed, not only the ones planned for that sprint.
Currently we use the standard SCRUM template and plan our sprints with it.
The current plan (sprint backlog) contains (of course ;-)) the current stories and tasks.
When I open the plan, as default the Work Breakdown view is selected. Then I switch to the “Taskboard” view. All stories and tasks are displayed correctly.
When I click on “refresh” (the RTC refresh, not the browser’s refresh), the display shows *all* stories and related tasks, not only the ones planned for that sprint.
That stays even when I use the browser’s “refresh”.
Could reproduce it with both IE and Firefox and 2 different users.
Anyone having the same experience? Or is this a configuration issue?
Regards
Heike
Accepted answer
This issue is already addressed using 2 defect:
Task board view of plan loads the work items from past Iterations (If parent hierarchy is > 2 and does not belong to the plan) (276834) this is part of 4.0.5
Task board view of plan loads the work items from past Iterations. (273908) the fix of this defect is part of 4.0.4