Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

storing knowledge in team foundation server

Tags:

tfs

We use Team Foundation Server. I was wondering if it's possible to store knowledge in whatever form in TFS. For example, if someone resolves a bug, it would be nice to document the solution and make it available/searchable for others (also in other team projects). The solution can indeed be applicable in other contexts.

We also use Sharepoint, so integration of these two is possible.

like image 794
bvgheluwe Avatar asked Jul 12 '12 08:07

bvgheluwe


People also ask

What is Microsoft Team Foundation Server used for?

Microsoft Team foundation server is a Application Life cycle Management (ALM) system that takes care of all aspects in software development. It includes Source Code Control(SCC), Versioning, Bug Tracking, Project Management and Team Collaboration platform features.

Is TFS a DevOps tool?

What is Azure DevOps Server? Previously known as Team Foundation Server (TFS), Azure DevOps Server is a set of collaborative software development tools, hosted on-premises. Azure DevOps Server integrates with your existing IDE or editor, enabling your cross-functional team to work effectively on projects of all sizes.

What is Team Foundation Server in testing?

Team Foundation Server (TFS) is an ALM product from Microsoft which provides the capabilities for an end-to-end development and testing using Work Item Management, Project Planning (Waterfall or Scrum), Version Control, Build/Release (Deploy) and Testing capabilities.

Is TFS a code repository?

Azure DevOps offers two options for versioning your code in a repository (“repo”) TFVC used to be the default type of repo for TFS projects. This has led many people to combine the terms for the two and refer to the TFVC repo as “TFS.”


1 Answers

For information localized to a workitem (say, a screenshot for a bug, etc.) tieing that data directly to a workitem is the way to go. For data who's lifespan is beyond that of a workitem (knowledge base stuff, ongoing documentation, etc.) consider sharepoint.

So to your example, if the defect resoultion had some data that was localized and had no real long term value, you would leave it in the workitem for historic reasons - but if it had longer term value, consider tieing this back to Sharepoint (wiki or to some other document), and optionally adding a link between the bug (or other workitem) and the sharepoint article (do this by using a link type of hyperlink).

Another option for searching out some of those workitem specific notes would be to use an extension (i.e. http://visualstudiogallery.msdn.microsoft.com/3f31bfff-5ecb-4e05-8356-04815851b8e7/ ), but IMO for the stuff with long term value, Sharepoint makes a lot more sense.

like image 113
Bob Palmer Avatar answered Oct 21 '22 18:10

Bob Palmer