I have uploaded a tool i've been working on for a year.
WI Migrator performs a migration of TFS work items environment from a Team Project to another, cross TFS collections / servers.
Great solution for migrating between two live TFS environments, including migration to the cloud, from the cloud or between clouds.
WI Migrator duplicates the work items, restores the links between them,
and recreates the test plans and the test suites. Work items attachments included.
TFS Servers supported: TFS 2010/2012/2013/2015/ Visual Studio Online.
You can give it a try.
a trial version is on vs gallery. with the trial you can migrate up...
TFS 2015 update 1 released
great features - backlogs & boards improvements, multiple dashboards,
Work item queries edit with relevant values only to choose (work item types / states), export test outcome (web), mixed GIT+TFVC in a team project
Found great tool - https://mergeworkitems.codeplex.com/
Suppose you work in your own branch, and associate each changeset you check in to work items. Then, after week or two of work you merge your changes to the integration branch - How will you associate the changes to the work items you associated while working in your branch?
Well, this tool does it. It's a server plugin that does the work for you after a merge operation you check in. the plugin links all work items associated to merged changesets - to the new changeset created.
However, a little bit of effort needed to deploy the...
TFS 2013 update 4 released.
Many new features to web access work item tracking, such as trend charts, area path search, better embedded url support, performance improvements & full screen support.
New licensing model - Stakeholder license - for using work item tracking without charge.
In addition - the ability to easily include bugs in the backlog.
Testing hub improved, and one of the major improvements is the charting wizard for test cases and test cases results.
I have written about team alerts issues found in TFS 2012
Here are some updates
1. Since TFS 2013, the issue of ignoring "preferred email" and using AD settings is fixed.
You can choose your preferred email and it will be used for sending team alerts
2. New issue since 2013 update 2: if team alert IS NOT included in contributors, alerts will not be sent - read here. fix/workaround - just include the team in Contributors group
In upcoming version - 2013.4 - managing work items, querying, using backlogs
and alerts in TFS web access - free of charge, no license needed.
New version Microsoft Visual Studio Team Foundation Server 2010 MSSCCI Provider 32-bit released.
This version includes a fix to an issue of workspace mapping curruption when using VS2005 with MSSCCI in a multi branch environment.
I hope this fix will be also released for MSSCCI 2012 + 2013 soon.
Since TFS 2012 the alerts system has been improved dramatically, allowing us to create alerts which affects all team members.
The alerts administration is web based and does not need any plug-in or a client tool.
However, I've been asked why do the individual alerts continue to work and to send email upon a trigger, whie an alert set for the team does not do the same.
When individual do not work, we check SMTP settings, we check the query which the alert is based on, and we look for errors in event log.
But now situation is different: individual alerts work, no...