To view tasks assigned to SXD_Group you need to update the "View Query" for your Work Items.
1- Right Click "My Work Items"
2- Select "View Query"
3- Add a new clause: "Or" - "Assigned To" - "=" - "SXD_Group"
4- Close and Save
enjoy !
Showing posts with label TFS 2005. Show all posts
Showing posts with label TFS 2005. Show all posts
Thursday, September 25, 2008
Assign Work Item to multiple TFS Users part. II
At this point we have customized the work item to allow asignments to
To view tasks assigned to SXD_Group you need to update the "View Query" for your Work Items.
1- Right Click "My Work Items"
To view tasks assigned to SXD_Group you need to update the "View Query" for your Work Items.
1- Right Click "My Work Items"
Friday, December 21, 2007
VSS to TFS Source Control migration
Team Foundation Server (commonly abbreviated TFS) is a Microsoft offering for source control, data collection, reporting, and project tracking, intended for collaborative software development projects. It is available either as stand-alone software, or as the server side backend platform for Visual Studio Team System(VSTS).
As Visual Source Safe is targeted towards individual developers or small teams with lightweight SCM needs, Microsoft is encouraging everyone else to migrate to the more sophisticated Team Foundation system.
There's a command line tool provided by TFS 2005 to migrate from VSS to TFS and is called VssConverter . The VSSConverter.exe is located in:\Program Files\Microsoft Visual Studio 8\Common7\IDE and is also available through the Visual Studio 2005 Command Prompt.
Due differences between this two technologies VSS historical information cannot be migrated. Basically, TFS source control does not support Sharing and Pinning. Because of this, Sharing, Branching (Sharing is a pre-condition of Branching) and Pinning historical information is lost when migrating to TFS source control.
Also, time stamps and source control bindings are not migrated.
Despite this limitations VssConverter.exe does a great job but it requires a lot of XML configuration.
The VSS Converter requires Microsoft Visual SourceSafe 2005 or a later version to run.
As Visual Source Safe is targeted towards individual developers or small teams with lightweight SCM needs, Microsoft is encouraging everyone else to migrate to the more sophisticated Team Foundation system.
There's a command line tool provided by TFS 2005 to migrate from VSS to TFS and is called VssConverter . The VSSConverter.exe is located in
Due differences between this two technologies VSS historical information cannot be migrated. Basically, TFS source control does not support Sharing and Pinning. Because of this, Sharing, Branching (Sharing is a pre-condition of Branching) and Pinning historical information is lost when migrating to TFS source control.
Also, time stamps and source control bindings are not migrated.
Despite this limitations VssConverter.exe does a great job but it requires a lot of XML configuration.
The VSS Converter requires Microsoft Visual SourceSafe 2005 or a later version to run.
Want TFS 2005 to support WSS 3.0 ?
As you may know, TFS 2005 release relies on Sharepoint Services 2.0 for team site integration among other things.
I was looking for a way to allow my TFS 2005 to support WSS 3.0 since this new release has enhanced integration and new features.
Interested in WSS 3.0 ? here you can learn about what it brings to us.
There's a way to achieve this upgrade by applying a hotfix to TFS, but some prior steps have to be made.
All information is available here.
I was looking for a way to allow my TFS 2005 to support WSS 3.0 since this new release has enhanced integration and new features.
Interested in WSS 3.0 ? here you can learn about what it brings to us.
There's a way to achieve this upgrade by applying a hotfix to TFS, but some prior steps have to be made.
All information is available here.
Subscribe to:
Posts (Atom)