I am creating a query from the backlog in 2 different TFS projects using the link on the backlog page:
It is generating differently for each project.
The 1st project was created in TFS2103 and upgraded to 2015:
The 2nd project was created new in TFS 2015 after the upgrade.
Note the difference in the query for the Area path. The one for the project created before the upgrade uses the 'Under' operator. The one create after the upgrade uses the '=' operator.
Can anyone explain what is causing the difference?
This is governed by the Area configuration for your team. You can find it in the Configuration panel:
Related
I setup TFS 2013 scrum template late last year and was using it without issue. When adding a new PBI or BUG on the Web Portal and tabbing into the Assigned To field I was able to start typing or drop down the list to see all the members of the Team Project.
After upgrading to TFS 2015 the list is gone and type ahead does not work. If I type the first few characters of a member and click search I am able to find a member, but this is cumbersome when going through and trying to quickly add a PBI or BUG. FYI this also happens when adding a new Bug as well as tasks on both a PBI and Bug.
I have a PBI in TFS under ProjectA with an iteration and area value filled in. Is it possible to move this PBI to ProjectB without creating a new PBI?
I am not seeing a way in the Visual Studio UI to do this. If I try to manually type in the area path of ProjectB, Visual Studio says that the path cannot be found.
I am using Team Foundation Server 2013 and Visual Studio Ultimate 2013.
No. Work items cannot be moved between team projects.
The reason is simple: The process template of the team project defines the work items. Team projects can have different templates. What if you tried to move a work item from a team project using a Scrum template to one using a CMMI template?
I would go a little deeper and say that if you need this feature then you should not have two Team Projects in the first place.
http://nakedalm.com/one-team-project/
The term that I use is:
"If you have artifacts that interact, with artifacts defined as people, code, or work items, then they should be in a single Team Project"
http://nakedalm.com/creating-nested-teams-visual-studio-alm/
Using a single Team Project can give you many more capabilities at the backlog/ work tracking perspective. Like the nested teams described above.
EDIT: This does not work for TFS2017 and forwards.
Yes, see http://www.codeproject.com/Tips/1018002/Yes-You-Can-Move-TFS-WorkItems-Between-Projects for a downloadable utility, source and a more detailed explaination.
It is a backdoor, SQL Manager approach, not supported by Microsoft, but it works for me. Here is the SQL:
UPDATE [Tfs_xxx].[dbo].[WorkItemsAre] SET AreaID=#AreaID,IterationID=#IterationID WHERE ID=#WorkItemID
UPDATE [Tfs_xxx].[dbo].[WorkItemsLatest] SET AreaID=#AreaID,IterationID=#IterationID WHERE ID=#WorkItemID
UPDATE [Tfs_xxx].[dbo].[WorkItemsWere] SET AreaID=#AreaID,IterationID=#IterationID WHERE ID=#WorkItemID
With the Tfs_xxx being replaced with Tfs_<your collection database name>.
Essentially, the project is inherited from the Area and the Iteration. Changing these from the current project to the target project causes the workitem to "move" to the target project. Additional rough edges are that the assignment pool or the workflow states might not align and have to be edited mannually in the UI to get the workitem back in the flow of the target project.
See my related answer.
Though not applicable to TFS on-premise, one can now do this with Azure Boards in Azure DevOps.
I've recently upgraded my TFS environment to 2012 (from 2010) and would like to take advantage of the project management features (ie. agile dev).
The issue I have is the current project has custom templates that cannot be automatically upgraded though tfs' wizards.
I was wondering, is there a way to clone a existing project or branch it so it retains all its change history while being able to implement the new agile templates?
Have you taken a look to http://tfsintegration.codeplex.com/ ?
I used that several times to migrate upgraded TFS2008 projects into TFS2010 to use the new templates. You can also create work item mappings to get them migrated too, so that the checkins will not lose the work item relations.
Small disadvantage is, that the history is flatten down to the date of the migration. I "solved" this by editing the adapter to insert the old checkin date into the comment.
Is it possible to rename a TFS2010 team project?
The project in question is based on the CMMI 5.0 team project template, but it has been modified with several custom modifications (new WITs and link types).
For a rename to be feasible, all history must be maintained.
In all: No, it can't be done.
Your only shot is to create a new Team Project named as you 'd like and then move everything to it. This involves serious work done by hand.
After that, you can't erase your old TeamProject - you will loose the history. You can lock it and make it unavailable to everybody.
After having done this a few times we think about the names of our Team Projects a lot. If at some point their name is(gets) wrong, I 'd say we 'll live with the mismatch.
Unfortunately, team projects in TFS are not able to be renamed in TFS 2005, TFS 2008, or TFS 2010. It's currently the #1 feature on the Visual Studio User Voice site for TFS. If this is something that's important, I'd recommend putting some votes on that feature: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2037605-rename-project-in-tfs
As far as I know you can create a new TeamProject and move your sources while maintaining history. Not sure if work items are preserved even when you delete/destroy the original TeamProject though.
As per the other comments "No, you can't", when we do it here we create a new project and then migrate source and work items over using the TFS Integration Platform, then delete the original project
I have an TFS server installation that through time has gone through upgrades from TFS 2005 to TFS 2008 and then to TFS 2010.
During the lifetime of the installation a lot of projects have been created and different project templates have been used. MSF Agile 4.0, 4.1, 4.2 and 5.0. and a few MSF CMMI ones.
What I would like to do is "replace" the project template used for all these projects to use a new one common one: Microsoft Visual Studio Scrum 1.0.
I am aware that TFS project templates are used as templates for creating new projects and cannot modify the tfs projects definitions after creation.
Uptil now only the version control and build server part of TFS have been used and there are no existing work item types.
Additionally all projects and build scripts are depending on the source code paths stay the same.
As I see it I have the following options:
Create new TFS projects using the correct project template and then move/branch the source code to the new project.
All code is moved to a temporary team project.
The old project is deleted
New project with the original name and correct process template is created
Code is moved to the new team project
Temporary team project is deleted
All the build definitions needs to be to recreated which is not an option.
The source code move/branch will "mess up" the versioning history
By messing up the versioning history I mean that when you move source code it will behind the scenes do a delete + source rename on the original location and the history will still be located in the old project. This will make searching in the history difficult and if I actually delete the old project I will loose all the history before the source code move.
This is really not an option for me since there is years of code change history that is needed to for supporting the different applications being built.
Use the TFS migration tools to migrate to another TFS project
This has the same downsides as the first solution
Replace/import work item types, install new reports, create new SharePoint sites
For each tfs project
Delete existing work item definitions using "witadmin deletewitd"
Import each work item definition from the new process template using "witadmin importwitd"
Import work item categories using "witadmin importcategories"
Delete old reports in project folder in report server
Upload the report definitions from the new process template
Modify data sources used for the reports using the report manager to point to the correct shared data sources (TfsReportDS and TfsOlapReportsDS)
Modify the report parameter ExplicitProject default value to "" (empty string) and disable prompt user option.
Export the documents in the old SharePoint site using stsadm
Delete the old SharePoint site
Recreate the sharepoint site using the TFS2010 Agile Dashboard site template
Activate site feature "Team Foundation Server Scrum dashboard"
In TFS Project Settings -> Project Portal Settings: Enable "team project portal" and ensure the url is correct. Enable "reports and dashboards refer to data for this team project"
And finally..
Process the Warehouse
Process the Analysis Database
Even though that this involves a lot of small steps this looks more appealing because
this option will not force me to move the source code and my existing build definitions will be intact.
My question:
Are there other ways to achieve the replacement of work item types that I haven't mentioned?
And/or am I missing any steps in last solution?
Given that you aren't using any existing work item types, your final proposal looks like the best option.
After deleting the old reports and exporting the SharePoint documents (you could also use Windows Explorer instead of stsadm), there are actually two commands in 'tfpt' that will help you. This will reduce it from 14 steps down to 5 or 6 steps.
tfpt addprojectreports Add or overwrite reports for an existing team project
tfpt addprojectportal Add or move portal for an existing team project
tfpt addprojectreports /collection:http://yourtfs:8080/tfs/YourCollection /teamproject:"Your Team Project" /processtemplate:"Microsoft Visual Studio Scrum 1.0" /verbose
tfpt addprojectreports /collection:http://yourtfs:8080/tfs/YourCollection /teamproject:"Your Team Project" /processtemplate:"Microsoft Visual Studio Scrum 1.0" /verbose
Your first option is IMHO your best shot.
You can branch the sources from the old team project to the new team project. With TFS 2010 you can see the history also from the branched location. So you don't loose functionality in here.
The Build is just an msbuild file which is stored in source control. The only thing you have to do is actually copy the build definitions. You can do that either manually, or you can create a little app that does that for you.