Submitting Silverlight Bugs and Suggestions
In case you don’t know, you can submit Silverlight Bugs and Suggestions through the main Developer Division Connect site. These Connect issues are sent to the Silverlight team so they can review them and make a decision on their resolution.
Most teams across the division are tracking their work items in a TFS project which is being used for the Visual Studio 2010 and .Net Framework 4.0 release. When the previous release was shipped, we migrated all the open and postponed issues (which were reactivated) to this new TFS project(including Connect issues). When the migration occurred, the Silverlight team was in the middle of their 2.0 release so it did not make sense to have them go through a migration of their work items in the middle of the lifecycle. As a result, the Silverlight team is not tracking their work items in the same database than the rest of the division.
The main Developer Division Connect site is configured so that new Connect issues filed through the site are opened in the main TFS project used by Developer Division product teams. They are then reviewed and targeted to the right product team(by setting the TFS Area Path) by a small team of engineers who then work on trying to reproduce the issue reported. When the product team changes the resolution or the state of the issue, it is reflected back on the public Connect site and it generates an email to the person who submitted it notifying him/her of the change. If the issue needs to be moved to another DevDiv team not tracking their work items in the main TFS project, the issue needs to be copied to the other database used by the other team and a dependent link needs to be created between the two issues. When this happens, the state and resolution you see in the Connect site is that of the primary issue in the new database. At that point, we can resolve and close the original Connect issue opened in the main TFS project as External as it is no longer used for synchronization with the Connect site.
Over the last few weeks, the tool which was used to move issues to the Silverlight team was not working properly: it was closing the issue without properly creating the link with the new issue in the Silverlight database which means that the state and resolution shown on the public Connect site is that of the bug in the main DevDiv database rather than the one in the Silverlight database.
I apologize for the inconvenience. I just fixed the problem so these Silverlight Connect issues should now be synchronized properly and showing the correct status from the Silverlight database.
