Hello,
I'm not sure why clicking "Sync from TFS" caused you to be able to see the Product Backlog Items and Tasks in WIM. This button is somewhat poorly named because it doesn't accurately describe what it does. Clicking this button simply causes the iterations in your iteration schedule to become in sync with the current iteration structure in TFS. Clicking "Sync from TFS" is required if you ever add, delete, or move an iteration.
I'm still confused at to why you are seeing different work items in WIM and in TFS. WIM uses the same object model and permissions as Team Explorer in Visual Studio (it actually references the Team Explorer assemblies). Can you attach some screenshots or a video illustrating your issue? It seems that there is something I'm missing. Also, can you explain to me which screens in WIM you are using to view your work items? I would also be interested in the results of the following test:
1) Open your project in WIM
2) In the Queries pane, pick a query that you expect to return some work items and run it. Ensure that the expected work items are returned.
3) Open the same project using Team Explorer in Visual Studio.
4) Run the same query from step 2. Ensure the same work items are returned that you saw in WIM.
5) Repeat steps 1-4 using a different user. Ensure this user gets the same results.
Re: iteration schedule and Sprint work items
Since most process templates don't have a Sprint work item type, we came up with the iteration schedule as an alternative way of giving dates to iterations. We did this at a time when only the EMC Scrum 2008 template had a Sprint work item type. Currenlty the iteration schedule does not work together with the Sprint work item type so unfortunately, if your process template does have a Sprint work item type you will have to maintain your iteration dates in two places.
Pieter, while we do use source control to save things like the iteration schedule, we ignore any check-in policies when checking in so I don't think the problem is here. Also, work items don't need to be checked-in.
Regards,
Joel
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the
Telerik Public Issue Tracking system and vote to affect the priority of the items