The title is confusing but I didn't have a good single line description. Let's say you have the following iteration tree defined:
In the admin iterations screen, you select "Iteration 1". If you assign a feature to "Product" or "Iteration 1", it'll show for the root backlog view (no filtering or choosing iteration or area.) If you assign to "Release v1", it doesn't show.
Hi John,
This behavior is intended. When you un-check an "Release v1" in the iteration admin page, the work items that are directly assigned to it won't show anywhere in Urban Turtle, no matter the filtering. If you need to see the work items under "Release v1", you will have to check "Release v1" in the iteration admin page.
Luc
I can't see how you'd intend behavior which completely hides work items. The way we work now, we assign features to a release and the PBIs/bugs to the iteration in which they're worked on. If we do what you suggest and select the release iteration, we lose our ability to schedule capacity at the iteration level.
Thanks for your answer. We realize that this is an issue when using the capacity feature of TFS. We will review our way handling it, but I can't say if or when it's going to change.
In the meantime, one way to work around the problem would be to create a new TFS team that would have the "Release v1" selected. People in the new team would be able to plan releases, while the development team would only see iterations at the same level than "Iteration 1".
That way, you will be able to use the capacity for the development team and plan at the release level with the new team.
Regards,
Luc
3 Comments