TFS: How to tie a Bug/Feature/Task to a Repository Subfolder?

if you edit a bug/task in tfs there is at right side a group box 'Classification' and two attributes 'Area' and 'Iteration'. especially the second allows you to go to sub-folders.

Sara

When I go to Iterations, all I see is Sprints?
 Not the subfolders.  That's why ai dont think something is setup correctly..

I acknowledge that TFS may be setup incorrectly or I may be using the repositories incorrectly - which is why I am seeking help. If something is setup incorrectly, then that is exactly what I expect help with.

I was asked to close the question either by accepting one of the comments as a solution, or by deleting the question, or by adding a new comment.

I came to the decision that the only comment (added by me) did not answer your question, since you seem to have a much different client interface than the one I was used to. That also includes that I can't help you further, as I don't have an idea how iterations which is the means to create subareas of your tasks could be defined with your client. The fact, that I was the only participient, may infer that other experts also can't help with the information given.

I think, the only way to get better help, is to ask a new question, where you post as many screenshots of your current environment and projects as to show where you were stuck. It also would be helpful if you could say whether it is the tfs server or the tfs client where you have problem with.

Sara

It may be an misunderstanding of the concepts in visual studio online.  The backlog, tasks and bugs are reported to the entire project.  You then associate the build or changeset (i.e., specific code) through Add Link.

So is the entire "repository" the "entire project"?  Is that maybe where I went wrong?  I added about a dozen different projects to the same repository.   i.e. a "Softphone App" and a "File Converter App" under the same repository.

Unfortunately it will blend those together.  When first started with VS online, we did that for all our projects and when you are working locally in VS and check in changes, it shows you excluding all the other projects because in TFS thinking all projects (whether in multiple solutions or not) belong on the same "project" defined on TFS.

Thank you. I will try separate repositories.

I just did a test and it may be a workaround for you.  If you create features, i.e., make your individual apps different features. That way, you can have your backlog items associated to specific feature.  Does that make sense?

Good luck!

Interesting suggestion on the features.  I will try that!

Yes, it could get you by until you are able to change setup OR as we did we left the initial set of projects in single repository how we had them (for fear of messing them up *laughing*) but created new projects as new projects.  Nice side benefit to that is we could tailor the project and repository type to what we were working on.  For the most part, I stick with TFS because of VS but with some apps written in code where Git makes more sense, you can do that plus use Scrum, Agile or whatever template.

Thank you!

You are most welcome!  I did notice that I do not get the browse on my version, so an easy trick to get the path is from Code just select the file you want then path is above it and it lets you copy and paste that into item path for the bug / work item's link to Versioned Item.  You then can set Latest Version or tie it to specific Changeset but found it is best to paste in link (i.e., set path) first before changing to Changeset as it makes the path textbox very small. *lol*