I am sure that is not the right place to ask. But I really need your guy's opinions on this. First of all, I am really appreciate your help.
asked Nov 22, 2010 at 03:05 PM in Default
Tasks are project specific, so you'll have to add tasks to specific projects.
You can, however, allow everybody to view all tasks across all projects.
Like adding a task, the normal view tasks query is also project specific. TFS allows you to work around this by creating a new query:
Once you've created the new query, remove the filter for "Team Project" = @Project, and change the "Value" column for "Work Item Type" to "Task"
once you save this query, it will be available in TFS web access. Give it a meaningful name, as you will probably have several queries to track tasks as they move through the development process (New, InDevelopment, Testing, Complete, etc).
Like adding tasks, adding queries is also project specific. Based on your need to have cross-project visibility, and to help with query manageability, I would recommend creating a "master project" to house all of your cross-project queries so team members have access to the entire repository from a single location in the TFS web portal.
You could also keep your tasks in a master project, but I would recommend leaving the tasks with their specific projects so you can correlate code changes with specific tasks.
I don't think you'll find much TFS expertise among us database guys here, but you'll almost certainly get a good quick answer on stackoverflow.com.
answered Nov 23, 2010 at 12:52 AM