How to make an active project area use a different template?

If there's a relatively small number of open work items that need to be
migrated, then I personally prefer to create a new project area with the
new template, and then move the open work items to that new project
area. The work-item move operation will look for any "incompatible"
fields, and will initialize them to a default value, which you can then
fix up.

I have had folks successfully modify the existing project area. This
involves:
- replacing the process configuration source (that's easy ... cut/paste)
- adding any missing process attachments (mechanical, but tedious if
there are a lot of them)
- fixing up existing metadata ... this is the hard part. In particular,
hard enough that lots of folks give up at this stage, so its not one I
recommend unless the old and new templates are reasonably similar (which
doesn't sound like is the case for you).

Going forward, you'll want to look at having your project areas "share"
their process configuration from some common project area. You can then
upgrade to a different project area by just changing the project area
you share from. As long as you upgrade in small increments, this
evolution becomes manageable.

Cheers,
Geoff

On 1/10/2012 2:53 PM, ghu wrote:

Most of our teams use a customized version of Eclipse process
template.
A few use different ones, like Scrum.

Now the team which using Scrum process template wants to use the same
customized version of Eclipse process template.

What is the guideline to switch:
1. Create a new project area using the customized version of Eclipse
process template; then Migrate the metadata from the original project
area using Scrum to the new project area?

2. Covert/reconfigure the existing project area to use the customized
version of Eclipse process template?

Anyone tried before?
Please share.