Geeks With Blogs


Add to Google

Tim Hibbard CEO for EnGraph software

Kyle and I are running into a small problem with Team Foundation Server when it comes to assigning tasks. 

In a typical software development company, a Project Manager receives a bug or feature request.  He then assigns associated tasks to his developers.  Once the developer is finished, the task is re-assigned to the PM for review.

At EnGraph, things are a bit more collaborative.  Partly because of our size, but also because we like to manage support and development from a team perspective. 

Back to our problem.  We really want to be able to assign a task to a group that contains myself and Kyle.  Both of us would get email alerts, both of us would be able to manage the task, it would show up in our respective "My Work Items" and either of us could close it.  This way we can create tasks that need to be done, but either of us could handle.  I originally created a ParaPlan Developers active directory group, but was unable to assign a task to it.  I know that we can set permissions so that he can view my tasks and vice versa, but we want to maintain individual tasks as well. 

I'm going to create a new user called ParaPlan_Stud and we will assign common tasks to it.  We will change our "My Work Items" query to view items assigned to @Me or assigned to ParaPlan_Stud.  We can use the bisubscribe tool to create email alerts for this user to go to both of us.

I don't know if it would be useful for bigger companies to have the ability to assign a task to a group rather than an individual, but it would certainly help us.

I'll try this for a couple of weeks and see how it goes.

Update:  Here is what we did.  It's been working well so far.

Posted on Monday, January 15, 2007 11:18 PM EnGraph , .NET , TFS | Back to top

Comments on this post: More "Team" in Team Foundation Server please

# re: More "Team" in Team Foundation Server please
Requesting Gravatar...
Hey Tim. You can assign your work items to a group, but it has to be a Team Foundation Server project group, not an Active Directory group. Then, anyone in that Team Project group can view and work on that work item. It requires some customization to your process template and work item types. Shoot me an email at if you have any questions.
Left by Mickey Gousset on Jan 16, 2007 4:33 AM

# re: More "Team" in Team Foundation Server please
Requesting Gravatar...
Hey, thanks Mickey. I'll give that a try.
Left by Tim Hibbard on Jan 16, 2007 10:00 AM

# re: More "Team" in Team Foundation Server please
Requesting Gravatar...
Hi Tim,

Like Mickey says just create a TFS Project group. This is what we do. I created some project groups all beginning with "Team -" so they all sort together in the list and I can do a AssignedTo contains "Team" in our My Work Items query.

Another idea is to create your list as a global list and define your field like this:

<FIELD name="Assigned To" refname="System.AssignedTo" type="String">
<DEFAULT from = "value" value = "Team - Software Support" />
<GLOBALLIST name="Project.Teams" />
<WHEN field="System.State" value="Resolved">
Left by Robert Kozak on Jan 16, 2007 2:25 PM

# VSTS Links - 01/18/2007
Requesting Gravatar...
Tim Hibbard on More "Team" in Team Foundation Server please.

The Accentient blog on Version Control...
Left by Team System News on Jan 18, 2007 9:05 AM

# re: More &quot;Team&quot; in Team Foundation Server please
Requesting Gravatar...
Where is the AD group integration? We already do enterprise management of team groups for many other access rights. It should be an option, but certainly not a requirement, to re-create special TFS groups separate from all the other group security. That's a huge step back. Any AD group should work as a group for Team Foundation purposes. Please advise if/when this is available.
Left by Paul Noeldner on Jan 25, 2007 10:05 AM

Your comment:
 (will show your gravatar)

Copyright © Tim Hibbard | Powered by: