VS11. Bring back the old "Pending Changes" window
The new one is very confusing!!!
I think the old one was almost perfect so why did you change it??? I mean, you can add new options but why did you change the philosophy?
The most important problems I see with the new one:
- No way to have that window independent so it can be accessed easily and fast
- Difficult to see at first sight the files changed! (of course, the new “no color” interface is part of the problem...)
- Difficult to exclude changes! (in the old one it was so easy by clicking the checkbox...)
We are happy to let you know that in today’s release of Visual Studio 2013 Preview we have made numerous improvements to the Pending Changes experience. The most significant additions are the ability to undock the Pending Changes page from Team Explorer, an option for viewing changes in a flat list, text filtering, and the removal of the “All Changes” page that was used when your number of files exceeded 250 items.
You can get the VS2013 Preview build here:http://go.microsoft.com/fwlink/?LinkId=306566
Program Manager | TFS Version Control
NOT completed. Although the "new" pending changes has a flat-file, dockable view, it is still not a good replacement for what we already had in 2010. This is like a poor man's Pending Changes, at best. It's like the Visual Studio/TFS team is not listening to us nor cares about our needs.
After 3 new versions of VS I am still using 2010 because of this one issue. I admit 2015 is a vast improvement over the awful 2012/2013 but still not up to par with 2010. I would love to upgrade soon so please, VS team, fix this one problem!!!
The source code for the old Pending Changes (TF.exe) is still included with VS 2015 so please at least give us an option of using the new or old pending changes, as a Preference setting.
Franjo Brekalo commented
I just want to checkin only one of the files which have pending changes. In the old view (VS2010) it was simple - remove checkbox mark on the files I don't want to checkin and that was it. Here, in VS2013 I don't know how to do it. Should I put to 'excluded' list all the other files and then checkin this only file and then put every file back to included list ?
Fred Foobar commented
Updated from VS2010 to VS2015, lots of things got better but this change is a major step backwards:
- Merging TeamExplorer and Pending Changes is bad: When they were independent navigation was fast (e.g. quickly change the the Project/Branch, access documents, etc.).
- The new TeamExplorer takes up much more space for doing the same things
- Including and excluding changes from a checkin has become horrible [while(true) print("!");]
Daniel Smith commented
The team clearly haven't listened to a word we've said, as the issue hasn't been addressed in any meaningful way what so ever. This is clearly not the outcome that we were looking for.
Jesse Stevenson commented
Thank you for making these changes. Is there a way to permanently undock the Pending Changes page? Whenever I check in it has re-docked itself.
In my humble opinion this issue is not "Completed", the pending changes window in VS2013 is still pretty much useless. Why did you change one of the things that actually worked in VS2010?
I've been crying over the new 'pending changes window'. It's the most horrific change you could come up with.
Bring back the old VS2010-style pending changes window!!!!!!!!!!!!!!
Why on earth would you do this??
In my company we updated to VS2012 from VS2008, and we have found the new Pending Changes management absolutely horrible to use and creates a lot of troubles.
Please bring back the old Pending Changes" window also for VS2012 ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
the new website sucks I want the old one back it was my favorite website to go on!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! bring it back!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! why did you get ride of it in the first place a lot of people liked it
Not having my work items listed there so that I can check them (without flipping over to a different query window or then keying the item # in) is a big suck.
In the next version of Visual Studio, please bring back a method for listing my assigned work items (whether I select a default query or something) so that I can simply checkbox the one I want to include these checkins on. Having to type it, copy-n-paste it, or drag and drop all suck as alternatives.
If your guys were struggling with that, here is an example of how to do it:
Chuan Li commented
Pending Changes in VS2013 is a joke.
It makes the simple task extremely troublesome due to the crowded metro layout, eye-hurting color scheme, confusing UI interaction:
- Spot the files to check in
- Include them, exclude other
- Compare with latest
- Enter comment
- Check them in.
Pending Changes in VS2010 is much more usable UI design.
Stanley Goldman commented
LOL, I gave up man, just go use Git and be happy.
That's the only way to teach them that their decisions have been horrible.
Either way, you get three votes from me on general principle.
Michael Jensen commented
In outrage to the way this request has been addressed (as well as many others), I've posted the following user voice request: Let the the USERS decide when a suggestion is "completed"!
Suggestions for improving the pending changes window in future versions.
1. Allow the first three sections (Policy Warnings, Comment, and Related Work Items) and the last section (Notes) to be pulled out of the main Pending Changes screen or put in a separate column so this exists beside the Included changes & Excluded changes windows so the Included changes & Excluded changes can be scrolled separately from the other pending changes info.
Allow freezing the first three sections (Policy Warnings, Comment, and Related Work Items) (similar to freezing rows in Excel) so that scrolling through the changes does not hide those sections.
(I like the first option better)
2. Allow adjusting the Warnings and Work Items sections so they can be shrunk down to one or two rows of info and scrolled individually so as not to take up the entire window when many Warnings or Work Items are listed.
3. Create an easier way to assign Work Items to the pending changes. A button in the Work Items list that adds the selected work item(s) to the pending changes if not already there would be great! It was much easier in 2010, but that version was not without its problems. E.g. If you changed the Work Items query, the previously assigned work items were no longer assigned.
I also am not a fan on the pending changes window, but I have decided to try to pass on helpful comments
So... after seeing that wonderful "Undock" button... is there any chance of really actually fixing this in Visual Studio 2014? 2015? Sure hope nobody got promoted for this "great new interface idea". Was the vision that someone was gonna be using Visual Studio from a tablet? For the real world record, most of my team is sticking with 2010 as their preferred IDE. If Microsoft truly understood how bad 2012/2013 has been on the street, they would have gathered in audience around the project manager and handed them a short sword. The Pending Changes window needs to be rolled back. It's not that confusing.
I know there are a million comments on how horrible the pending changes is, but I would like to add one more. 2012 has great improvements for IntelliSense in C, but the interface is so blaahhh. No colors anywhere, looks like one big pile of boring ****. Pending changes makes me day so unhappy anytime I need to check something in. There are thousands and thousands of files in our solution, this tree view would be good only for small projects.
"Microsoft does not use Visual Studio to develop so they do not know how bad their changes are." -@BilliJack
This is true!
Even the simple Ctrl+F with Quick Replace option is gone (now you have to use Ctrl+H instead). I know you guys (in MS) are brilliant, but pls. don't make thing complicated!
Daniel Tannenbaum commented
I mean there are some simple things that you just wonder, where did they go?
Like for example: I have a policy that says use the "Current backlog" query when checking in. This is nice because I can enforce that only items that are active can be checked-in against.
For some strange reason, you can no longer use queries defined in "Team Queries" now you can only use queries in "My Queries" which means that I can no longer enforce this policy. And in general I cannot use shared queries. WHY IN THE WORLD? What does MS have to say about that?
Also: drag work item? are you for real? well at least let me drag it from Team Explorer (because I have to admit the new search capability there is very nice) NO! You have to open it as a query and than drag it...What does MS say about that?
Come on Visual Studio Team. The treeview is ridiculous. It is confusing and non productive.
I still use Visual Studio 2010 for my source control related tasks.
And now you are saying that I have to buy the new version. Is that a joke?
Have you guys worked on big solutions with a lot of projects and deep folders? I only modify a handful of files, and I want to see them in a quick glance list view. Whenever I see a tree, I get frustrated, because I don't know where can I find my file in that tree.
William Bosacker commented
@EMI: You might want to look into Shelvesets. You can "shelve" all of your current changes that you don't want to check in, do a "Get Latest Version", make the bug fix changes, check in the bug fixes, then restore your shelveset, do a "Get Latest Version" to merge in any changes, and pickup where you left off.