Share via

Upgrading TFS 2005/2008 Project Sites to TFS 2010, Part 4 - Project Work Items Web Part

  • Article

In the part 1 of this series, I described how to enable the dashboard functionality in Team Foundation Server (TFS) 2010 on project sites upgraded from TFS 2005/2008 (i.e. sites originally created with the MSF Agile v4.x process templates). I noted that it wasn't quite as simple as activating a feature on the SharePoint site because some of the TFS Web Parts on the new dashboards specify the new User Story work item type introduced in the MSF Agile v5 process template, instead of the old Scenario work item type.

[Honestly, I'm not sure why the TFS team felt compelled to change the name of the work items. My preference would have been to keep the original work item type and extend it as necessary (e.g. to add a "Story Points" field) -- if for no other reason than to avoid having to update numerous Web Parts and Excel reports on upgraded TFS project sites. Obviously the TFS product group didn't ask for my opinion on the matter ;-)

Personally, I have yet to meet anyone who can't understand that a scenario is essentially the same as a user story. Then again, I still like to use interim milestones (e.g. M0, M1, M2, ...) rather than iterations (Iteration 0, Iteration 1, Iteration 2, ...), so I guess I'm just "old school" in some regards.]

Assuming you want to keep using your existing TFS project (with its Scenario work item type) but also leverage the great new dashboard features in TFS 2010, then you need to update the query criteria specified by the TFS Web Parts and Excel workbooks. In this post, I'll provide you with a short PowerShell script that makes it really easy to upgrade the numerous Web Parts that need to be updated on the various dashboard pages.

Let's start with the Burndown dashboard (which hopefully you'll set as the default page for the upgraded project site, since it provides an excellent summary view of the overall health of your project).

On the right side of the Burndown dashboard, you'll find the Project Work Items Web Part. This is simply an instance of the Microsoft.TeamFoundation.WebAccess.WebParts.WorkItemSummaryWebPart with the Query property set to the following:

 SELECT [System.Id], [System.Title]
FROM WorkItems
WHERE
(
    [System.TeamProject] = @project
    AND
    (
        [System.WorkItemType] = 'Bug'
        OR [System.WorkItemType] = 'Task'
        OR [System.WorkItemType] = 'Test Case'
        OR [System.WorkItemType] = 'User Story'
    )
)
ORDER BY [System.Id]

See the problem with this Web Part and upgraded MSF Agile v4 TFS projects?

Too bad the query specified for the Web Part doesn't explicitly exclude "unwanted" work item types (i.e. Issue and Shared Steps) instead of including a list of specific work item types. In other words, if the Web Part specified the following query, then Scenario work items would automatically be shown on upgraded project sites:

 SELECT [System.Id], [System.Title]
FROM WorkItems
WHERE
(
    [System.TeamProject] = @project
    AND
    (
        [System.WorkItemType] <> 'Issue'
    OR [System.WorkItemType] <> 'Shared Steps'
    )
)
ORDER BY [System.Id]

Consequently, for upgraded project sites we need to update the Web Part query to include Scenario work items instead of User Story work items. I suggest applying a very minimal change to the Web Part query in order to specify the following:

 SELECT [System.Id], [System.Title]
FROM WorkItems
WHERE
(
    [System.TeamProject] = @project
    AND
    (
        [System.WorkItemType] = 'Bug'
        OR [System.WorkItemType] = 'Task'
        OR [System.WorkItemType] = 'Test Case'
        OR [System.WorkItemType] = 'Scenario'
    )
)
ORDER BY [System.Id]

If you've done much SharePoint development, or if you've seen my previous post on the SharePointWebPartManager class, then you are likely familiar with programmatically manipulating Web Parts using the SPLimitedWebPartManager class.

Before listing the PowerShell script that will update the query on the Project Work Items Web Part, it is important to note that the Web Part is actually displayed on each of the dashboard pages:

  • Burndown
  • Quality
  • Bugs
  • Test
  • Build
  • My Dashboard

 Since each instance of the Web Part specifies its own query, we need to update the Web Part on each of the pages:

 # Updates the "Project Work Items" Web Part on the dashboard pages of TFS
# project sites originally created with the MSF Agile v4.x process template
# in order to show "Scenario" work items (instead of "User Story" work items)

function UpdateWorkItemSummaryWebPartOnEachDashboardPage(
    [Microsoft.SharePoint.SPWeb] $web)
{
    Write-Debug "Updating work item summary Web Parts on site ($($web.Url))..."
    
    $pagesToUpdate =
    @(
        "Dashboards/Burndown.aspx",
        "Dashboards/Quality.aspx",
        "Dashboards/Bugs.aspx",
        "Dashboards/Test.aspx",
        "Dashboards/Build.aspx",
        "Dashboards/MyDashboard.aspx"
    )
    
    $pagesToUpdate |
        ForEach-Object {                        
            $wpm = $web.GetLimitedWebPartManager(
                $_,
                [System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared)
            
            UpdateWorkItemSummaryWebParts $wpm
            $wpm.Dispose()
        }
}

function UpdateWorkItemSummaryWebParts(
    [Microsoft.SharePoint.WebPartPages.SPLimitedWebPartManager] $wpm)
{
    Write-Debug "Updating work item summary Web Part on page ($($wpm.ServerRelativeUrl))..."
    
    $wpm.WebParts |
        Where-Object {
            $_ -is [Microsoft.TeamFoundation.WebAccess.WebParts.WorkItemSummaryWebPart]} |
        ForEach-Object {
            UpdateWorkItemSummaryWebPart $wpm $_      
        }
}

function UpdateWorkItemSummaryWebPart(
    [Microsoft.SharePoint.WebPartPages.SPLimitedWebPartManager] $wpm,
    [Microsoft.TeamFoundation.WebAccess.WebParts.WorkItemSummaryWebPart] $webPart)
{
    Write-Debug "Updating Web Part ($($webPart.Title))..."

    $webPart.Query = $webPart.Query.Replace("User Story", "Scenario")
    $wpm.SaveChanges($webPart)
    
    Write-Debug "Successfully updated Web Part ($($webPart.Title))."
}

$sitesToUpgrade =
    @(
        "https://cyclops/sites/AdventureWorks",
        "https://cyclops/sites/Demo",
        "https://cyclops/sites/Toolbox"
    )

$sitesToUpgrade |
    ForEach-Object {
        $DebugPreference = "SilentlyContinue"
        $web = Get-SPWeb $_

        $DebugPreference = "Continue"
        UpdateWorkItemSummaryWebPartOnEachDashboardPage $web

        $web.Dispose()
    }

After running this script, the Project Work Items Web Part on each dashboard page will show scenarios in addition to the other work item types in the MSF Agile v4 process template.

Comments

  • Anonymous
    June 06, 2010
    Hi, I'm trying to use your PowerShell script in a Visual Studio project to configure my dashboards in C#. Can you explain where i find the Microsoft.TeamFoundation.WebAccess.WebParts.WorkItemSummaryWebPart class? I searched in all dll files but i don't find this class :( Thank you.

  • Anonymous
    June 06, 2010
    WorkItemSummaryWebPart is located in Microsoft.TeamFoundation.WebAccess.WebParts.dll.

  • Anonymous
    June 06, 2010
    Thanks for quick reply. But on my virtual machine there is no such dll file. I've installed TFS 2010 RC1, MOSS 2007 and Visual Studio 2008/2010. Very strange?! The TFS web parts are working in SharePoint but i can't use the classes from this dll because i miss this dll.

  • Anonymous
    June 06, 2010
    On my TFS server, Microsoft.TeamFoundation.WebAccess.WebParts is installed in the GAC.

  • Anonymous
    June 06, 2010
    The comment has been removed