Binding to IsChecked property doesn't work in TwoWay mode (ConvertBack doesn't work).

Declined.
IsChecked / CheckState are supported only in xaml-defined RadTreeViews. In databinding scenarios use the approach described here =>
http://www.telerik.com/help/wpf/radtreeview-howto-tri-state-mvvm.html

Allow selecting and unselecting items on right click when the SelectionMode is Multiple/Extended.

Reason for decline: This can easily be implemented as application logc using th MouseRightButtonDown event of the RadTreeView.

It should be possible to collapse certain items to filter them out. This should not affect the look or functionality of the 

This is already implemented => you can use the ItemVisibility property of the RadTreeView.

Programmatically reorder items with animation.

Declined. This could be implemented as application logic. The requirement is too specific to be included in the publi API of the RadTreeView.

The request is related to the method AddItemByPath - To build the whole hierarchy not only to add the string after last separator.

Too specific requirement that could be implemented as application logic.

Ability to temporary view particular element as root item. Functionality have to be similar to "View this as root" in the Solution Navigator window in Productivity Power Tools for Visual Studio.

This is too custom requirement that can be implemented as application logic. 
Setting fildetered itemssource and preserving the current itemssource could be a possible solution.

Dynamically change of the theme of the RadTreeViewItems cannot be achieved.

Reason for decline:
The bug is outdated. Every RadTreeViewItem can be Styled via its Style property or the ItemContainerStyle of the RadTreeView.

When a copy of the Control Template of the RadTreeView is edited in Blend, the followin error is thrown: TargetName property cannot be set on a Style Setter.

Reason for closing: The bug is not reprodible with VS 2012, WPF 4.5 and latest official version of telerik UI for wpf.

Expand bottom up.
=================

Reason for deletion: 0 votes for more than 4 years. 
Users can invoke in a loop ExpandItemByPath in order to achieve expanding from bottom to top.

When using binding to check state and dynamically adding subitem to a praticular items, the parent items check state is incorrectly set to Off (from ON) although the child item state is also On.

Marking this Declined. Binding to CheckState is not supported in MVVM scenarios. Please use the approach described here =>
http://www.telerik.com/help/wpf/radtreeview-howto-tri-state-mvvm.html

When the IsVirtualizing property is switched on runtime (for example as a result of applied binding) the generatedContainers are not updated and potentially will not return null when a container exists.
===
Marking this Declined: There is no such public collection. Too old item with only a single vote (like).

It was suggested that the ItemTemplates in the tree view should update when the item template selector or the item template is changed.

This will be hard to implement properly because of the numerous ways in which a template can be set. A naive implementation is more doable, though we are not notified when the ItemTemplate property changes
====
Reason for marking this Declined: Too little information, too old item (5.5 years) with too litle votes.

Support CommandBindings.

The item is Completed =>
RadTreeViewitem is ICommnadSource since 2011. 
RadTreeViewItem already has Command property, the command fires on mouse click.

When using binding to CheckState property and TriStateMode is enabled the checking of parent (its business object) does not affect unrealized childrens' CheckState, because the bindings have greater priority than the TriState logic. Same in the other direction - checking the child has no effect over the parent.

Marking this as Declined.
TriState Mode is supported in XAML-defined or code behind defined trees with direct creation of 3Viewitems. 
In DataBound scenarios, 3-State should be created by the user with ViewModels as described in this help article.

http://www.telerik.com/help/wpf/radtreeview-howto-tri-state-mvvm.html

When you tab through your application you can observe that when the focus moves to the TreeView it will focus the first TreeViewItem. However, when you change the ItemsSource collection of the TreeView at run-time you won't be able to tab through the TreeView or its first TreeViewItem at all.

Fixed in LIB version: 2014.2.0915

The TreeView should be able to figure out the Old / NewValue for its event args during editing.
====
======

Reason for deletion. In databound scenarios e.OldValue and e.NewValue refer to the same instance of the ViewModel which is expected. 

Saving the state of the ViewModels means creating an entire deep copy of the ViewModel. We believe there is no such control in the framework to save the states of its ViewModels during editing.

We have to admin, introducing public properties OldValue and NewValue of type objects for these event args is a bad design. This is a bug since these are public but we won't fix it due to the complexity (described above).

Update the radtreeview-howto-exapand-select-item-with-lod-enabled-treeview

Allow cancelling a drag operation originating from certain items - basically the customers need to disable the drag operation on some items.
====
Here is a possible solution with handling DragInitialize
 
DragDropManager.AddDragInitializeHandler(this.tree, this.OnDragInitialize, true);

 private void OnDragInit(object sender, DragInitializeEventArgs e)
        {
            if (((e.OriginalSource as RadTreeViewItem).Header == "B1")
            {
                e.Data = null;
                e.DragVisual = null;
            }

Repro actions:
1) Hit the "End" key to go to the bottom
2) Hit the "Home" key to go back to the top
3) Mouse wheel does not move the scroll
4) The scroll arrows don't work either
5) They keyboard arrows don't work either, the selected item is displayed but they scroll bar does not move

See this video for reference.

Setting these properties in the Legacy mode works as expected. The NEW DND mode will be the default one in Q2 2014.