Iteration Names Cached - By Design?

When I change an iteration name in the Team Explorer (Team Project Settings -> Classifications), the new name does not display in my work items until I get out of Visual Studio and fire it back up again. I thought maybe it was cached by design, but if I change the ProjectModelHierarchy names, a Work item's "Classification Area" updates without having to get out of Visual Studio. It this a know "issue"?
[410 byte] By [JasonD.Camp] at [2007-12-16]
# 1
A couple things may be going on:
1. In beta 2, workitem tracking does a latent sync by polling every 10 minutes. This has been rewritten by beta3 to be on change with minimal latency.
2. After the data get's into workitem tracking, metadata like this is cached on the client on the file system and incrementally updated when certain actions are performed such as doing a query, opening a workitem etc... data is piggy backed to the client.

Try and do another operation like a query or opening etc... and then open a workitem and see if it appears. It could be that or the latency. In beta3, the latency should be minimized greatly.

Bryan MacFarlane
Dev Lead, Workitem Tracking

BryanMacFarlaneMSFT at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...
# 2

Your first case was correct. Waited 10 mintues and it updated. Thanks for the info.

It still is a little curious why the iteration names are cached and not the classification areas, but that's just me.

JasonD.Camp at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...

Visual Studio Team System

Site Classified