Cannot create Team Project: State 'In Progress' does not exist

Cannot create Team Project: State 'In Progress' does not exist by thys

Closed

as Fixed

Type:	Bug
ID:	773391
Opened:	12/4/2012 1:38:16 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

When creating a new team project using the Scrum 2.0 or MSF Agile 6 template, the creation stops because of the following error:

Error

TF30170: The plugin Microsoft.ProjectCreationWizard.WorkItemTracking failed during task ProcessConfiguration from group WorkItemTracking.

Explanation

Plugin error text: "The following element contains an error: TaskWorkItems/States. TF400587: This element defines the states for work items that appear as tasks on your sprint backlog. Each state must exist in at least one of the work item types belong to category defined in: TaskWorkItems. The following states do not exist in any of the work item types: In Progress."

User Action

Contact your Team Foundation Server administrator.

I checked the work item definition Task, the category to which Task belongs and the query, and all seems well. Nevertheless, I cannot create a new project.

This collection was upgraded from TFS2010 and includes custom project templates.

Details (expand)

Team Foundation Server 2012

upgrade TFS2010 project collection with custom process templates to TFS2012
create new team project with new Scrum template
after a while project creation stops with error

English

Windows Server 2008 R2 SP1

English

Error

TF30170: The plugin Microsoft.ProjectCreationWizard.WorkItemTracking failed during task ProcessConfiguration from group WorkItemTracking.

New team project

0 attachments

This is a bug with the way validation is performed for the process template during project creation. The issue is most likely that the string 'In Progress' was already known to the server as a 'constant', but it's using a different case (like 'in progress'). When we attempt to provision the 'In Progress' string it will re-use the existing constant 'in progress', but the validation being done on the process settings is using a case sensitive comparison to verify that 'In Progress' exists, which fails.

The easiest workaround is to find the current case for the string and change the CommonConfigurate.xml file in the process template to match that casing.

You can find the constant in the constants table by running the following query in SSMS:

SELECT *
FROM [Tfs_DefaultCollection].[dbo].[Constants]
WHERE String like 'In Progress'

though you will need to replace [Tfs_DefaultCollection] with the database for the collection where the problem is occuring.

To fix the problem in the process template, make a note of the casing of the string you found with the above query, then use the process template manager to download the template. Change the CommonConfiguration.xml file in the downloaded template so the 'In Progress' string matches properly, then upload the process template.