I am the admin of TFS 2015 Upgrade 3. I would like to create a new collection and move some of the existing team projects from an existing collection to this new one using generic MS tools (not third party). Is this feature available, and if so can you post a hyperlink for steps?
Thank you,
Genearlly we can not move projects from one collection to another.
However you can split a team project collection. Simply say you can clone from the existing colleciton, then delete other unneeded projects from the cloned colleciton.
Follw the steps mentioned in this article to do that:
Split a team project collection
Related
I have 2 different tfs server setup , one runs with tfs 2015 other with tfs 2017.
I need to move a specific project from 2015 to the 2017 instance.
Please guide me with the best approach that we can go with...
You could not directly move things based on team project level , this seems like an inherent design issue with the source and work item entities. Since there is also not able to move a Team Project between Team Project Collections, there has been a uservoice:
Make it possible to move a Team Project between Team Project Collections
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/2037613-make-it-possible-to-move-a-team-project-between-te
You have to move the entire team project collection if you want to keep all workitems, source control history for that specific project. If you just want code, the simplest way is copy them and add it in a newly created team project in TFS2017.
I had developed one small application which will fetch data from TFS project workitemcollection object and store it into SQL table.
Now I want to update database regularly. What I have done is, I have created as service which will create new tfs project workitemcollection object and update database based upon two checks i.e. if defect id is already present in table it will update the SQL row with new values and if not it will insert the new values.
ISSUE: In one scenario the defect from one tfs project has been moved to another tfs project but SQL still contains that id in old project.
Ways I can think of: another check from opposite direction to verify if defectId is not present in collection then delete it.
OR,
Every time service run delete the old table and fill the complete table with new and updated data.
What will be the best option or if there is third one?
You can consider creating a server side plugin for TFS to listen to the work item change event. Once the event triggered, create/update/delete the record in your SQL table.
If you use TFS 2013 and previous versions, check TFS 2013 event handling on work item change to create the server plugin.
If you use TFS 2015 and later versions, including the solution above in TFS 2013, you can also use Web Hooks to send a JSON representation of an event to any service.
I get a weird error message when trying to create new Visual Studio 2010 project of type "SharePoint 2010 Sequential workflow":
"The SharePoint site at "somesite" is missing a target, task, or history list. Each of these lists is required to associate a workflow template. Please create a list and then launch this wizard."
I already have two projects in my Visual Studio 2010 solution: MyListsDef with many SharePoint custom lists defined and MySiteDef with site definition to populate those lists when new SharePoint site is created.
I have to create SharePoint workflow project for some of my lists in Visual Studio 2010.
I made some steps prior creation of third (SharePoint Sequential workflow) project in my solution:
Compile and package both MyListsDef and MySiteDef,
Install both MyListsDef.wsp and MySiteDef.wsp as solutions on my SharePoint 2010 server,
Create new SharePoint 2010 site based on MySiteDef template,
Create new Visual Studio 2010 project "SharePoint 2010 Sequential workflow" with reference to SharePoint site, created in step #3.
However, I always get the error "... is missing a target, task, or history list." every time I select a site, created in step #3, as a reference in a sequential workflow wizard in Visual Studio 2010 in step #4.
What does this error mean and what lists are missing?
What I am doing wrong?
What is a typical way to develop SharePoint workflows with custom lists?
Thanks in advance,
Sal
Sal,
This happens when required lists for workflows are not created.
Do the below to make it work :
ACTIVATE any feature thats relaetd to workflow (1st at SITE COLL level then at WEB level)
Go to the site and select a list
Click on WORKFLOW SETTINGS in the RIBBON
Then ADD A WORKFLOW and then select some workflow (ex: approval)
SAVE it
The above process will create required lists for workflow processing.
Now you can continue with Visual Studio work.
I am looking for a migration tool. We want to upgrade from SharePoint Server 2007 to SharePoint 2010 in a new environment. We need to have functionality to granulary select which content to migrate and eaven select to map to new structure in the new solution.
We want to tag the content migrated.
The migration tools we are considering are AvePoint, Axceler Davinci, Metalogix.
I'm doing migration scenarios for a consultant firm based in Montreal. First of all, I think you have the correct thinking about how you want to get this done. Doing a SharePoint upgrade (database upgrade) usually bring your SharePoint 2007 problems over to SharePoint 2010.
Here's what we usually do :
Define governance for the new SharePoint platform
Define the new Information Architecture
Implement the new Information Architecture (build sites, lists, libraries, etc.)
Migrate the content over
Tools such as Sharegate (www.share-gate.com) can allow you to do some mapping from your old content source over to the new one.
Hopefully, this will help you!
How do I change process template to MSF for Agile on an already existing team project in TFS 2010?
We have upgraded our TFS 2008 to 2010, and now I would also like to change the process template to MSF for Agile (currently CMMI).
We haven't used the workitem functionality much so if some information gets lost in the conversion doesn't matter.
Once you've created a Team Project, you unfortunately can't just upload a new process template. As Robaticus says, you'll have to download the XML for the template and modify it, then re-upload it. The power tool lets you create NEW templates for NEW team projects, but it won't modify an existing one.
Instead, you can use the witadmin.exe tool (on any computer with Team Explorer installed, under \Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE, or just from a Visual Studio Command Prompt) to export the current workitem definitions and re-import them once you've made your changes.
Luckily, if you're not using workitem tracking much, then this might not be too difficult. You might be able to just delete all the existing workitem types and then re-upload the new types.
If this is too much trouble, consider how much you want to retain your source control history. It might be worth creating a new Team Project with the Agile template and then just moving all your source code into it.
You can't change the process template, however you can change the work item types. So for bugs, tasks you can swap to the Agile definitions.
You can do this in 2010 with witadmin, in 2008 it's importwit, by first downloading the template to disk (you'll need the TFS power tools for this). Then point the console app at bug.xml, task.xml etc..
Usage: witadmin importwitd /collection:collectionurl [/p:project] /f:filename [/e:encoding] [/v]
/collection Specifies the Team Foundation project collection. Use a fully specified URL such as
http://servername:8080/tfs/Collection0.
/p Specifies the team project in which the new work item type is imported. This is required, except when
the validation-only option is used.
/f Specifies the work item type XML definition file to import.
/e Specifies the name of the .NET Framework 2.0 encoding used to import the XML file. For example,
/e:utf-7 will use Unicode (UTF-7) encoding. Encoding is automatically detected whenever possible. If
the encoding cannot be detected, UTF-8 is used.
/v Validates the XML definitions for the work item type, link type, or global workflow without importing
them.
You can export the agile process template to disk, then import the work items into your existing project. You may need the TFS Power Tools to do this.
I may be too late for this question, but the TFS Integration Platform tools could really help here.
See this question on server fault that details on how to move from Scrum For Team System V2 to Microsoft Visual Studio Scrum 1.0.
You would need to setup your own mappings to move from your templates to the target template, but the process is the same.
Please note witadmin.exe could help in some scenarios but TFS Integration Platform is your ultimate choice to achieve this task. There is a user voice item still pending. Please check this SO thread.
I think the best way to accomplish this is to create a new Team Project with "the new" process template and use the TFS Integration tool to migrate your existing WorkItems and choose create a new branch from Source Control, so you'll have new work Items (with the new workflow) and the source control history (as well). You'd even do this across versions of TFS!! (On the case interested on migrate TFS 2005/2008/2010)
Another way might be to use the WorkItem Templates, but I think this is more a kind-of visual style (I've not much experience) applied to the Work Item. To do so, just right click on your project, import the WITDefinition and apply the template by selecting Apply template on desired WorkITems.