Kimball

We are encountering a number of situations at our client sites that involve modifying Process Templates to 'correct' the client's attempts at designing new workflows.

That is, clients have used template modification tools such as PTE to add work item types and global lists and work item type fields and work item type states and transitions and reasons.

Then they have used witimport to upload the changes to specific TFS projects. Of course, they need to modify each TFS project to make the changes apply consistently to each new project.

By the time we arrive on the scene, they have realized they now understand their process more better and they want to make a more organized modification.

So the problem that is arising centers on the historical data that was collected during the period after they made their initial changes.

Can we create a new work item type and associate the fields in the new type with data that was collected in columns using fields that were created for use with the previous work item type

There are more questions i have about this, but could we start there



Re: Team Foundation Server - Process Templates Moving States and Transitions to new Work Item Types - what gets left behind?

Subodh Sohoni

I dont think that you can move workitem history data like that to a new workitem type. Data for that is already aggragated in TfsWarehouse and should not be touched.

One approach would be to keep the same workitem types, reuse those fields. If they can not be used then keep the fields, simply create new appropriate fields and take form elements of old fields out. Those fileds may still be accessible programmatically using TFS Object Model but will not appear in the workitem forms.






Re: Team Foundation Server - Process Templates Moving States and Transitions to new Work Item Types - what gets left behind?

Kimball

When you mention 'reuse the fields', are you suggesting that the work item type fields can be accessed from a new work item type

That would certainly be an ideal situation.

If we could just create a new work item type, refer to the existing fields, and then store similar data into the existing 'columns' in the TFS database/datawarehouse, then at least we could programmatically access the 'entire' line of the history for that field, even though the work items would be of different types.

Or am I not yet understanding the organization of the application





Re: Team Foundation Server - Process Templates Moving States and Transitions to new Work Item Types - what gets left behind?

Naren Datha - MSFT

Yes, your understanding is correct. That is actually intended use of fields and we encourage as much reuse as possible. It also helps in queries, because you can query for fields across multiple workitemtypes.




Re: Team Foundation Server - Process Templates Moving States and Transitions to new Work Item Types - what gets left behind?

Kimball

Well, then maybe you can explain the behavior of Work Item Fields and Global Lists in relation to when the Process Template is installed in TFS versus when it is applied to a TFS project.

If I use Process Template Manager to download a process template that has been installed in TFS but no TFS Project has been created, the Work Item Fields and the Global Lists do not show the complete list of Work Item Type Fields and Global List items that exist within all the installed Process Templates.

My experience is that only the System.X.X work item type fields and the CMMI.x.x WIT Fields are shown.

However after projects have various templates assigned and after solutions are included in source control under those projects, the WIT Fields list and the Global List items do include WIT fields etc from all the installed templates.

What is going on with this





Re: Team Foundation Server - Process Templates Moving States and Transitions to new Work Item Types - what gets left behind?

Dennis Habib MSFT

Hi Kimball,

The process templates that are stored on the server do not create fields (or anything else) until a project is created with them. When the Project Creation Wizard is run, it does a 'witimport' on the work item types that are included in the process template. That's when the fields contained in the template are provisioned on the server. Just uploading a new process template does not create the fields. It does validate the work item types to ensure they are likely to be work (formatted correctly, etc), but in the end a process template is stored on the server as a zip file in the database and only used by the client during project creation.

The 'System.xxx' fields are 'core' fields and must exist for all projects. They are provisioned at setup time.

-Dennis





Re: Team Foundation Server - Process Templates Moving States and Transitions to new Work Item Types - what gets left behind?

ravizone

Hello,

I have installed TFS on my machine and created a Team Project with using the Agile Process Template provided. Now i would like to add and delete some of the fields that are displayed under the team queries.

Thanks,

Nani