We have the grid data-source and the headers bound to the members of the data-source data .
So the grid header on sort pass the data-field to the server .There should be option to change the header option and the data-field .

Cause we might send a VM  of the navigational property to client side and the grid on header click should send original data-field then the VM property

The current method of selecting the item to filter forgeinkey column is not useful for a lot of records.
It is necessary to enable the filter template customization, or add search/autocomplete to current filter template.

Kendo UI Grid - In batch update mode, currently, during save operation three separate events are fired for created, updated and deleted records. This really creates a problem when all the changes needs to be transactions. There needs to be an option, in which only one event is fired for all the changes.

The data-cascade-from-field option requires a DOM id to function. Due to the nature of in-cell editing, the DropDownList appears only when the field is clicked.

A potential fix would be to allow us to configure cascade through the model rather than the UI.

Need Control + F function to search the text in the Grid

When we have more records and enabled virtual scrolling ,the data which is not present the view is currently not searchable using CTR+F.

We need to get this enabled where finds the data and scroll down to the specific row.

When using setOptions and loadOptions to allow users to save their personal configurations of a grid, it would be nice if I didn't have to manually add all of the templates to the options object before calling setOptions. Without that step, columns using view templates appear with the raw data. To add the templates to the options object, I'm forced to separate them out as functions instead of leaving them inline with the column definition.

We are running into a situation where our users need to copy values from a row in a Grid. The Grid also uses multiple row selection, and the allowCopy is getting in the way by copying too much data onto the clipboard. 

Would it be possible to set a field list in the options for allowCopy so that we can specify which columns are actually copied?

Example: 
allowCopy: {
  delimiter: '\t'.
  fields: [
    'column1', 'column2'
  ]
}

We are also running into another situation where we need to use templated fields, and allowCopy seems to be copying the cell text resulting in very ugly clipboard data. It would be nice if we could specify the datasource value to be copied instead of the cell text

Example:

allowCopy: {
  delimiter: '\t'.
  fields: [
    { field: 'column1', source: true },
    { field: 'column2' }
  ]
}

In both examples, the field name corresponds to the field name specified for the Grid Column.

If another value gets created, we want to be able to update the columns.values array without destroying the grid and recreating it.

Currently with large number of records in the grid when column is resized quickly resize may not actually occur.In this case, the browser's JavaScript engine is not able to fire the appropriate events fast enough, due to the large number of records, which impose a performance hit on the page.
Suggested solution: 
it is possible to improve the column resizing performance if the columns are not resized real-time during dragging, but only after the user drops the resize handle.

Autofitting grid's columns according to its contents might be a pretty expensive operation, especially if there is are many rows. 

How about extending the 'autoFitColumn' function by a parameter which specifies how many rows should be taken into account when determining column's width. That would speedup autofit operations while maintaining a pretty good (good enough) estimation on column's width.

Provide build-in support for filtering and sorting for complex columns like dropdown or Autocompelete with dropdown in grid. Bound value consists of complex objects - one for value and one for text of the dropdown. Right now, sorting is based on value and not text. Please provide options to sort based on text. Filtering doesn't work for these columns. It would be nice to have filtering support for these columns.

In the JQuery Grid if you have the following column definition (for example):

[
    {
        "field": "Name",
        "title": "Name"
    },
    {
        "title": "Address",
        "columns": [
            {
                "field": "Street",
                "title": "Number & Street"
            },
            {
                "field": "City",
                "title": "City"
            },
            {
                "field": "PostCode",
                "title": "Post Code"
            }
        ]
    },
    {
        "title": "Contact Details",
        "columns": [
            {
                "field": "Email",
                "title": "Email Address"
            },
            {
                "field": "Phone",
                "title": "Phone Number"
            }
        ]
    },
    {
        "field": "DOB",
        "title": "Date of Birth"
    }
]

When you drag the multi-column header "Address" and drop it over "Date of Birth" the header and it's child columns move as expected but the column headers in the two multi-columns get mixed up.

This only seems to happen when dragging a multi-column past another multi-column in either direction.

The new event should fire as soon as the grid is fully rendered und ready to take user input or focus.

We need this for automated UI Testing. SetTimeout does not work reliable.

Add ability to have a horizontal scrollbar in the kendoui grid that appears at both the top and bottom of the data set to ease scrolling in large data sets.

Add property that defines a delay before requesting new items when scrolling. 

This would prevent sending multiple request when dragging the scrollbar and passing more than one page.

Currently the new select column and the "selectable" setting of the grid are mutually exclusive.  This seems completly counter intutive.  If you you have a select column and the "selectable" mode set to "multiple", then when you drag select or ctrl click on row the checkbox to be selected.  Right now it's not.  

when putting grid into new item creation state it should be possible to put new item with some predefined fields.

Current it is realy difficult to achieve that:

using datasource and insert do not contain isNew on model, also put it on top of grid page is difficult, not possible

using model.set. on edit event causing fireing save event when it should be fired only when item is realy saved.

When grouping one column on a large table, all rows (groups) are expanded by default which consumes CPU/memory. Render time grows.

Please add bool property defaultCollapsed. In this case grid would not expand all rows(groups) by default.

Current work around is to call collapseGroup, but performance would be a lot better if rows could be collapsed by default.

The issue is reproducible when the grid consists only from Multi-header columns, the setDataSource() method has been used and one of the columns is initially hidden.

After setting the new data source, the last header gets hidden. The "display: none;" style has been applied to the "th" HTML element.

Steps to reproduce:

1. Create a grid with multi-header columns only.

2. Hide one column initially.

3. Set a new data source via the setDataSource() method.

4. The last column gets hidden.

Sample Dojo:

https://dojo.telerik.com/AcipENOt

Kendo UI version: 2019.1.220

When endless scrolling and grouping is enabled on the KendoUI grid, collapsing large groups causes the grid to load ALL the hidden detail rows into the DOM.

This takes a very long time for the grid to do, as well it violates the whole point of a paging system. (ie I only want you to load X records at a time). Afterwards the performance of entire website (including the grid) will be very poor since potentially thousands of rows have been loaded into the grid and then immediately hidden. Additionally, these rows do not add any value to the user, since they are all hidden anyways.

When a category is collapsed, the grid should NOT add any new rows for that category to the DOM.

I have included a sample that demonstrates the performance issues.