Add Related Work Item to different Project?  
Author Message
Brad Smith





PostPosted: Team Foundation Server - Work Item Tracking, Add Related Work Item to different Project? Top

So I'm considering setting my TFS up so that we have a Project for each of several products, and also a project for each of several common assemblies.

Normally, a bug would be logged against one of the Products, since the person logging the bug wouldn't (in theory) be aware of the underlying modular structure. Somebody would review the new bugs and decide which module(s) they actually belong to.
So I'd like to be able to open a bug and choose Add Related Work Item to make a related bug, but in a *different project*.

I get the distinct impression I can't get there from here. Perhaps others have pondered this and have other options.

One that I can think of is to have one project for "everything" and use the "Area" to set up a hierarchy (so each product is an Area, there's an Area for "Common Modules" and under that an Area for each module).

I can make that work if that's the best approach. I just want to make sure I have my ducks in a row first because it's *real* painful to change anything once you have it initially set up.

Comments
Brad.



Visual Studio Team System35  
 
 
Naren Datha - MSFT





PostPosted: Team Foundation Server - Work Item Tracking, Add Related Work Item to different Project? Top

Brad, you can make related links between projects that are in same server. If they are in different server, you could still make a related link using the hyperlink of the workitem (the link you see in workitem change alerts for example).

You could use area paths as you mentioned. If you are linking just to projects, since projects are not in some hierarchy form you could instead use a normal field with list values of projects and save area for true hierarchy. The advantage will links is the ability to navigate to the target item and having more than one link.



 
 
Amit Ghosh





PostPosted: Team Foundation Server - Work Item Tracking, Add Related Work Item to different Project? Top

Brad, another thing to consider when deciding whether you should create multiple Projects or try to consolidate everything in one Project is whether you want to maintain the same WorkitemType definitions in all of them (eg. Should your Bug be identical in all products or can they be different ) If you wanted to easily maintain the same definition, you might want to consolidate things into one Project and have different areas for each Product.

In the next version of TFS, we are planning to create more isolation between Projects (Right now, the boundary is the TFS Server). Links between WIs of different Projects would still be allowed, but the functionality you might get from them might be lower than what you would get for links inside the same project. (We are planning to add additional Link functionality like queries across links, etc)

Thanks,
Amit

Dev, Team Foundation Server


 
 
Brad Smith





PostPosted: Team Foundation Server - Work Item Tracking, Add Related Work Item to different Project? Top

Thanks to both for the replies. Definitely food for thought.

Naren, you say that I can make a Related Work Item in a different project on the same server (we only have the one server, so that part is a given). However, there's no "Project" field in the Bug work item form that allows me to select. Presumably I'd have to modify the work item to add it
I thought maybe adding a field for System.TeamProject would do the trick, but it seems to be a string (rather than dropdown) and seems to be read-only (and doesn't actually show anything useful when I import & make a new bug).

I'm using Process Template Editor, which maybe isn't the right tool for this kind of customization. Or I'm just lacking some fundamental understanding somewhere along the line. Any advice appreciated.

We're a really small company (not quite small enough to make do with Workgroup edition, but close). So indeed we'd be aiming for consistency in the work item types. But I'm definitely conscious of the potential problem there.

Worst case, I suppose I could whip up an app that can do what I want. I'll add that to my ToDo list. :->

Brad.

 
 
Naren Datha - MSFT





PostPosted: Team Foundation Server - Work Item Tracking, Add Related Work Item to different Project? Top

Brad,

The project name is specified in Area path field and in iteration path field, and in System.TeamProject as you mentioned. Work items cannot be moved to other projects (just by changning that field), so that is the reason System.TeamProject is not a dropdown & readonly. You can however right click and do "copy workitem" and choose the target project for a copy of workitem.



 
 
Brad Smith





PostPosted: Team Foundation Server - Work Item Tracking, Add Related Work Item to different Project? Top

Bingo! This is the missing piece of the puzzle. I'd not looked at "Make Copy Of Work Item..." at all before. I see now that not only does it let me copy to a different project, it also allows me to copy to a different type (eg. Bug to Requirement) *and* maintains the link back to the original. I can definitely work with that.

Many thanks;
Brad.