Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » VSTS Planning & Tracking   (RSS)

Customizing Work Item Link Types in TFS 2010

A long time ago (almost 2 years ago), I blogged about how to customize link types. Since the Beta1 has been released, I thought it would be useful to reblog this information. Here are the links. The information is still valid. Rosario - Customizing Link

Forward Compat GDRs for Team Foundation Server 2010!

TFS will be providing a General Distribution Release (GDR) to enable older versions of Visual Studio Team System Team Explorer to work with 2010 TFS. Releasing these GDRs will allow teams to move forward even when some people are not ready due to legacy
Posted by jonieren | 5 Comments

Team Explorer 2010 Beta 1 Compatibility

Although many scenarios have been enabled in the VSTS Beta 1, there are a number of compatibility issues which are still being working on.     * List of Known Issues and Workarounds 1) Team Foundation Server 2010 administrative functions are

Team Foundation Server 2010 - Relational Warehouse and Cube Schema Changes

Team Foundation Server 2010 is a BIG release for us by all counts. We have made conceptual changes; Brian introduced some of the key concepts in TFS 2010 that includes the concept of Team Project Collections (TPCs). These changes required a lot of infrastructure

Previous State and State Change Count

Today I am going to look at two interesting fields in the Warehouse related to Work Items – Previous State, and State Change Count. The Previous State field stores the state a Work Item was in before it entered its current state. This field is in the

Work Item rules workaround: Cannot close task unless Remaining Work is zero

In the last post in this series , Gregg blogged about restricting a bug such that only the creator can close it . This is the last post in this series of workarounds that we have been blogging about. We saved this as the grand finale for our series.  
Posted by sunder | 1 Comments

Work Item Rules Workaround: Only the creator of the bug can close the bug

In our last post in this series, Sunder blogged about saving the resolved reason . (You’ve probably figured out that we have “tag-teamed” this blog series). So anyway, here is the next item in the series.  Customers have asked us: “I only want the

CodePlex Tool: WIT Synchronizer

I just saw that Loic Baumann posted a tool on codeplex called WIT Synchronizer . It provides two pieces of functionality that has often been requested. “I’ve made a change to my Process Template, how do I push those changes to existing projects” “I’ve

Work Item rules workaround: Saving the resolved reason

In our last post in this series, Gregg blogged about securing a work item type . Another question along these lines: “How can I save the resolved reason? I want to create metrics based on how bugs were resolved, but the value of the ‘Reason’ field is

Work Item Rules Workarounds: Secure creation of a work item type

In our last post in this series, Sunder blogged about Deactivating a work item type . Here’s another popular request: “Secure creation of a work item type”. For example, people say: “Only my Testers can create bugs” “Only my Business Analysts can create

Work Item rules workaround: Deactivating a work item type

In our last post in this series, Gregg blogged about forcing selection of reason . Let’s take a look at another question that we often get: “How do I deactivate/retire a work item type? I don’t want to destroy the type because I want to report on it,
Posted by sunder | 1 Comments

TFS Warehouse Work Item Tracking Compensating Records

Compensating Records What are compensating records? First a little background. Whenever a work item is updated a new revision is created. These revisions are moved over to the Warehouse and stored in the various Work Item Dimension and Fact tables. Each

Work Item Rules Workarounds: Force selection of Reason

In our last post in this series, Sunder blogged about Closing down an iteration . Let’s take a look at another question: “ How do I force people to select a reason? ” We’ve had people come to us with the request to force their users to select a reason.

Work Item rules workaround: Closing down an iteration

In our last post in this series, Gregg blogged about validating area path . Let’s take a look at another question: “ How do I close an iteration so that no one can log new items against it? ” For this example, let’s say we have completed Iteration 0 and
Posted by sunder | 15 Comments

Building lightweight dashboards using Excel

TFS work items can provide a wealth of information that can be used for decision making and analysis, answering questions like: Are we on track? Is our bug debt growing or shrinking? What is our incoming/fix/close rate? and many others… One way of keeping
More Posts Next page »
 
Page view tracker