Resource level updates refresh rate in Web vs Eclipse client
We are noticing different resource capacity displays between the Eclipse and Web clients. After a series of "Saves" and "Refreshes" we are seeing the following in the Work Breakdown view of our Iteration 1 Plan for one particular resource:
Eclipse Client: Closed items: 3 | Open items: 6 Load: 108 / 86 | -22h Web Client: Closed items: 3 | Open items: 6 Load: 108 / 81 | -27h It appears that the Web client updates faster than the Eclipse client at the resource level. However, the overall project progress bar in both clients (Eclipse and Web) update at the same time. Any reason why we are seeing refresh delays at the resource level in the Eclipse client and is there anything we can do to prevent this, or is there any advice to offer? Thanks, Tim |
One answer
|
Here is a quick follow-up to my post of yesterday. After many hours (6+) of refreshes, and restarts, the resource mentioned above is still showing 86 hours on the Eclipse client, and 81 hours on the Web client.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.