New items (rows) are not shown in grid when they don't match the filter settings made to the grid.
So it would be really useful if applied filters and sortings were resetted when new items are created.

By default Kendo Grid places a new created item/row at top of the grid in batch / incell edit mode. When saved the item remains top. The items count is increased in this case.
A click on Cancel puts the new item to the end of the grid and the items count is decreased.
There is just a work-around which stops the propagation of the cancel event when the datasource has no chances (thanks to Petur). 
That should be the standard behaviour.

Currently having a column format of "{0:#}" does not infect the filters format. E.g. 5 becomes to 5.00 on blur event in filter dialog. So we have to modify filters behaviour manually which is a pain. Currently we are using this function:


function configureFilterFormatting($grid) {
    var kendoGrid = $grid.getKendoGrid();
 
    kendoGrid.bind('filterMenuInit', function (event) {
        var column;
 
        $j.each(event.sender.columns, function (index, item) {
            if (item.field == event.field) {
                column = item;
                return;
            }
        })
 
        if (!column) {
            throw new Error('Invalid column');
        }
 
        if (column.format) {
            // Transform '{0:#}' in '#'
            var format = column.format.replace(/^{0:/, '').replace(/}$/, '');
 
            event.container.find('[data-role=numerictextbox]').each(function () {
                var $numericTextbox = $j(this);
                $numericTextbox.getKendoNumericTextBox().setOptions({ format: format })
            });
        }
    });
}

I know it is possible to show/hide columns through the column menu, but there is something odd about being able to hide one column from another column's menu. Alternative is to implement something yourself and use the API to show/hide a column, this seems like something that should be an option in the grid. I am imagining a column chooser button (perhaps in the top left header) that opens up a list of checkboxes similar to what you see in the column menu.

Kendo Grid should expose some method which are exposed by other controls...like selectable and disable...for k-selectable class.
So that one can enable or disable grid on external button click.

When a grid is first showed with a group value (e.g. a date value), it should be possible to apply a sorting direction to the grouped value (e.g. descending)

please add navigate property to custom command that fill new page address with current row id to href of a tag to easily link to relation page

I like what FooTable.js does with a html table.  (hide fields based on breakpoints) and place them so that they are available via click on +

would be nice to having an option to prevent specific column from re-ordering or re-sizing. 

In general, grid having command columns for Edit, Delete... etc buttons, these columns should not allow to reorder across columns.

Currently if you add a row to a grid in batch edit mode any rows that have already been edited will lose their dirty flag indicator.  I would like for Kendo to handle maintaining the dirty flag for these rows.  If there is a performance concern with adding this functionality, then maybe there could be a setting to turn it on or off.

Need to have the grid automatically draw itself correctly even if it is initially hidden.  Right now if it is hidden first, even with static height, when it is shown using javascript it is not draw correctly.  (especially with scrolling enabled)

Suggested route:  Add a repaint method that way people can call this as needed.

Currently kendo UI web grid component does not read the DescriptionAttribute of a enum type. So, if a have a enum named Gender with values {F, M}, kendo grid will show those values instead "Female", "Male". Example

public enum FooType
{
    [System.ComponentModel.Description("Foo Description")]
    Foo = 0,
    [System.ComponentModel.Description("Bar Description")]
    Bar = 1
}

As the example above kendo grid should use "Foo Description" or "Bar Description" for showing those enum values. Same apply to generating dropdowns for the Filtering columns feature.

Thanks and sorry for my english.

We need to improve enduser search experience in grids by increase control over filter menu.
In order to speed-up query providing we need to control which item is activated in Filter menu by default.
Very often default operator is set in grid configuration but enduser has to always change focus to second field  when he wants to provide search criteria. It becomes tedious activity when he search a lot.
Therefore we need access via api for controlling focus behavior in Filter menu.
It should allow to control this behavior without breaking existing tab sequence of controls.

I have recenty found that if users include <html> tags in fields in a form, and this data is then displayed in a grid, if the user then groups by that column, raw html will be displayed. The "suggested" way around this potential huge security flaw is to use a group header template for every string column, ensuring the value is displayed encoded using ${value} instead of the default #=value#.

The default for a cell is ${value}

Currently you can clone the Pager to make it appear both on Top/Bottom. This should be configurable so that you can have in on top of the grid or the bottom of grid or both

Currently we do not have the ability for descending to be first. It's either one, both in the asc/desc order, or none. You can changed the setting in the kendo javascript file but it'd be useful to have it be a property.

Grouping row in grid can expand/collapse after click on any area on the row not only after click on plus/minus icon. This behavior is similar to checkbox in browser with label for attribute

For columns that have long titles but minimal data it would be good to be able to orientate the text 90-degrees so it's top to bottom rather than left to right (like excel)

The current implementation of the DataSource only allows for footer aggregates during the fetch of data. When we f.i. use virtual scrolling in a grid for each fetch of data from the server we also have to calculate the aggregates. In many cases that is a time consuming process. F.i. we have a project that has an activitylist containing over 100.000 rows. We only show 25 rows with skip(page) and take(25) but on each roundtrip we calculate the aggregate for all 100.000 rows.

A better solution would be to get the aggregate asynchronous from the data fetch and only fetch the first time and when a change has taken place in one or more fields that have an aggregate result.

It would be great if user can format all the number is pager with 'N0', like following.

'page 1 or 1,200 pages'

'1,200-1,300 of 1,500 items'