group pending changes instead of having a flat list of files
The pending changes view only offers one flat list of changed files. If you work on more than one topic in parallel it is quite cumbersome to check-in only the files from your workspace that cover that topic. Shelving does not really help here. Having the possibility to assign changes to certain groups would help a lot.
FWIW, I can see how this would be useful in some ways, but I would prefer to have the flat list most of the time
Ciaran O'Donnell commented
This is my number one requirement as a programmer. When I started using Perforce I missed TFS. Moving back to TFS now I cant understand how I ever lived without this.
Copy what perforce has. That would be brilliant.
My biggest pain point is a that for our large solution with many projects, I wish to create a custom build configuration that I will never be checking in, but doing so adds over 80 items to the pending changes list...
James Barrow commented
IntelliJ IDEA I believe had this concept, and was a real boost to managing source control, great suggestion.
Perforce, you're the best.
It appears that once again Microsoft didn't think of the user.
You should have at least copy it from Perforce if you couldn't think of it yourselves.
Matthew Mitrik commented
Multiple "changelists" is a feature that we're tracking on our backlog, but don't have in the plans to support for vNext.
Program Manager | TFS Version Control
I second this. Working while on a submission ban becomes a pain when it's time to check that sh*zz in.