Consider a grid with grouping and pagination. When we collapse a group, the items from next page should take up the space left be the hidden rows, i.e., grouping should work across pages and not just the current page. Otherwise, grouping is a useless feature in a grid with pagination. This should work for client as well as server pagination and also for virtual scroll.

In your article: http://www.telerik.com/forums/how-to-make-a-non-editable-column-field, many developers make the point that the read-only attribute of a column should be part of the view, not model/data.
By not providing a column property to prevent editing, you have put the view logic in the wrong place.
Solution: Create a read-only property to each column to prevent editing.

It would be nice to have the progress when exporting the grid to excel so that the user knows that something is happening.

When performing Edit on a real-time grid, hide edit button to prevent simultaneous editing and data overwrite. 

There was a similar solution previous to signalR integration, http://www.telerik.com/forums/using-kendoui-grid-with-signalr#-3DZMT4HHE-rOWdEf_1mgQ

But with SignalR enabled grid, this could all be  built-in.

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)

It would be nice to have the option to configure different column titles for the column menu. For example, when there is a multi-header Grid, you could use this functionality to add the header title to the column title.

https://www.screencast.com/t/qgeK9fFMPP
https://www.screencast.com/t/NRl61JFzFH

Thus avoiding the need to work around the timing problem with a timeout like this:
columnReorder: function(e) {
 setTimeout(function() {
                // save data logic implementation.
            }, 100);
}

I want to have checkboxes in group header as shown in the below example.

https://dojo.telerik.com/eKUzITAH/41

Once I click on the group header checkbox, the child group headers under the clicked group header and the data rows inside it should get checked and when it is unchecked all the datarows under the group header should get unchecked.

Individually if I check and uncheck a checkbox in the datarow,the parent group header should get checked if all the datarows are checked and should get unchecked if any of the data is unchecked under that group header.

Updating a single row by default expands ALL collapsed groups. Removing a single row or inserting a single row does the same. This design lacks granularity: an isolated change to a single row should not cause the expanded/collapsed state of all groups to change.

If the user is focusing on flu cases in New York City and a new flu case is added to the Los Angeles group, why should every group in the grid be expanded? 

 Only the group affected by the change should change its UI state. The grid should listen for the change event of the observed  *row* and if it is felt that a change to the row's data should cause a UI change, only the group to which that row belongs should be changed.

Hello,

from our development I could collect some suggestions for improvement, which we would be pleased about in the future:

MVC
-> Grid
-> Export to Excel
- Do not show columns in export - currently only possible with Javascript
- Display additional columns in the export that are only displayed in the export and not in the interface 

At the moment, Remote Validation on the grid does not work with incell editing.

I would like to see this restriction removed.

Normal validation works with incell editing; however, the remote does not. I should not have to change the appearance and functionality of the grid from incell to to inline just because the standard validation is insufficient.

I appreciate that this is not an easy change, but hope you are able to give it some priority.

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.

It would be nice if its possible to slide threw the pages in a grid by using a slider in the footer.

In addition to columns.minScreenWidth, the grid also needs columns.maxScreenWidth for the situation described here: 
"http://www.telerik.com/forums/need-columns-maxscreenwidth-too!"

Kendo grid doesn't have in-built functionality to prevent row selection based on some condition.
One way is to remove css class "k-state-selected".
But i think there should be something like "changing" event which will be called before "change" event.
In that event developer write code and can cancel "change" event.
Or 
Boolean property something like "enabled" at row level (or cell level for cell selection) .

The existing configuration(filterable.extra), can only support 1 or 2 input from the UI. It would be great if multiple filter criterion input from the grid UI will be supported in the coming releases.

The Grid already has beforeEdit event that can be used for preventing the editing depending on custom logic. The same thing could be used for preventing add or delete based on custom logic or validation.

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.

Highlight a row during mouse over has to be done through CSS. However it doesn't work properly when there is a locked column, as there are two separate tables. This requires some programming. I suggest you embed it in Kendo, so we could easily use this feature without having to implement it ourselves.

Bug report

When the horizontal scroll of the grid is shown and is configured for RTL, the resize handle is mispositioned. 

Reproduction of the problem

1. Make the grid scrollable and set explicit widths to all columns.

2. Make the grid RTL.

3. Introduce multi-column headers.

4. Notice that the columns cannot be resized due to the disposition of the handler.

5. Dojo for replication:

https://dojo.telerik.com/IZInOVUd

6. Notice that whenever the horizontal scroll is not present, the resize handle is positioned correctly.

Environment

* **Kendo UI version:** 2019.3.1023
* **jQuery version:** 1.12.4
* **Browser:** [all]