There are two possible ways to hide older iterations. The Favorites feature (the stars that you see on each iteration) is the most obvious one to use. Simply click on the star for each iteration that you wish to hide, turning the star grey. Then, click the Apply Favorites button to only show the selected iterations (the ones with the yellow stars). This also works for areas.

Unable to display content. Adobe Flash is required.

Hiding a large number of iterations using favorites may lead to performance issues. A proposed work-around is to use the Team functionality to hide a part of the iteration tree. Teams can be configured to have a distinct root iteration. By default, the project node is the root iteration. If the root iteration is changed, the nodes that are not under it will not appear in Urban Turtle. So a recommended solution would be to have a structure similar as the following:

If the Current Iterations node is made the root node for the team,  the node Past Iterations or its children. This is a lot faster than hiding individual iterations using the Favorites feature. In Visual Studio, it is possible to move individual nodes. So moving an iteration that is under Current Iterations to the Past Iterations node when it is completed will hide it from Urban Turtle.

Note: The team button (as seen in the previous screen cast) needs to be enabled through the global.settings file.

The global.settings file used in this video looks like this:

<?xml version="1.0" encoding="utf-8"?>
<globalsettings>
    <collection name="DefaultCollection">
         <project id="4771">
             <teams>
                 <team name="My Scrum Team" rootiteration="Current Iterations" />
             </teams>
         </project>
    </collection>
</globalsettings>

See also

• Team Management, Per Collection and Per Project Activation