Some VS 2013 SDK IPendingChangesExt properties never change from initial value

I'm writing a VS 2013 Package that is trying to do some logic based on the FilteredIncludedChanges property of the Pending Changes Extensibility service (Microsoft.TeamFoundation.VersionControl.Controls.Extensibility.IPendingChangesExt), but this list is always empty, and the IncludedChangesFilterText is always empty.

Here is a screenshot of me filtering the Included Changes:

And here is the code from my section in the pending changes window that I'm using to get the extensibility service when the user clicks one of my buttons (i.e. the Included button) and get what the filter text is (i.e. "Model" in screen shot above) and the filtered included changes (i.e. ViewModel.cs in screen shot above):

_pendingChangesService = this.GetService<IPendingChangesExt>();
var filteredChanged = _pendingChangesService.FilteredIncludedChanges; // This is always an empty array.
var filterText = _pendingChangesService.IncludedChangesFilterText; // This is always an empty string.

The _pendingChangesService contains the 2 PendingChanges in the IncludedChanges array property, but the FilteredIncludedChanges property is always empty.

I'm also listening to the PropertyChanged event of the IPendingChangesExt, and the IncludedChanges event fires, but the FilteredIncludedChanges event never fires.  TheFilteredExcludedChanges and ExcludedChangesFilterText have the same problems, as well as the SelectedIncludedChanges andSelectedExcludedChanges.  These properties simply never change from their initial default values, no matter what I do on the UI.

It seems like these properties are simply not hooked up in the SDK API (i.e. should throw a NotImplementedException).  Am I doing something wrong here?  Can you reproduce this? The documentation page does say, "[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]" for the VS2013 version, so perhaps these property's functionality really just isn't implemented yet.  However these same properties exist in the VS2012 SDK too and the 2012 documentation doesn't have that little disclaimer, so I imagine they would be working already now in the VS 2013 SDK.

Any suggestions are appreciated. Thanks.

- Dan - "Can't never could do anything"