Hello We have several sites that I am in the process of moving from Sourcesafe and Mantis into VSTS. There are three web sites that are separate, but related. Currently, they have three separate Mantis projects so that the managers can track their progress individually. The code for all three site reside in the one Sourcesafe database, as they all share a common middle tier. Moving forward to TFS, I want to create the three separate TFS projects so that the managers can track each project individually. But the problem becomes where to put the common middle tier code. Do I put it in one of the projects, or create a separate project for that. Either way, work item data is lost for some or all of the projects. I may have to make changes to the middle tier for one of the projects, but cannot assign the work item to the checkin, as the code is in another project. Having a separate project for the common middle tier is not good, as it is not itself a project, and those project metrics are lost from the real project(s). Then I could put the whole lot in a single TFS project with the three sites represented as "Areas". This might be better. This way any change to the middle tier can have the work item associated with the middle tier code, and that web site that requested it. The only issue here is the reporting of one of the web sites within this larger project. Each web site is managed separately, with different stakeholders, and has different start and end times for development cycles. Is it easy to report separately on the three areas? Essentially, the metrics for the three projects jumbled together are useless. Any ideas/suggestions? Thanks David
************************************************************************* The information contained in this e-mail, and any attachments to it, is intended for the use of the addressee and is confidential. If you are not the intended recipient you must not use, disclose, read, forward, copy or retain any of the information. If you received this e-mail in error, please delete it and notify the sender by return e-mail or telephone. The Commonwealth does not warrant that any attachments are free from viruses or any other defects. You assume all liability for any loss, damage or other consequences which may arise from opening or using the attachments. The security of emails transmitted in an unencrypted environment cannot be guaranteed. By forwarding or replying to this email, you acknowledge and accept these risks. ************************************************************************* OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com - List managed by www.readify.net
