In Development
Last Updated: 18 Mar 2026 11:17 by ADMIN
Scheduled for 2026 Q2
Created by: Daniel Knoll
Comments: 0
Category: TaskBoard
Type: Bug Report
0

Bug report

Reordering in the same column is not working correctly

Reproduction of the problem

  1. Open the Demos - https://demos.telerik.com/kendo-ui/taskboard/remote-data-binding
  2. In the first column, move "Campaigns" below "Customer Research."
  3. Check the Network tab of your browser, and no update is sent. The "Campaigns" is moved back to the top. Sometimes an update is sent but it contains the wrong index, so the item is still on top.

Current behavior

The task order remains the same

Expected/desired behavior

IT should be possible to reorder the tasks in the same column

The issue is a regression starting with 2025.2.520 version

Environment

  • Kendo UI version: 2025.4.1111
  • Browser: [all ]
In Development
Last Updated: 17 Mar 2026 08:43 by ADMIN

I realize this has been covered by this workaround in the past, but the need to write extra code for moving the column back to the original position makes this seem a bit "hacky" and most importantly, the user experience of being allowed to drag the column in the first place just to see it jump back seems wrong.

The good news is that the kendoGrid already has a mechanism for preventing the columnReorder event from getting fired in the first place! The bad news is that it only happens for columns that have either of these 2 classes ["k-group-cell, "k-hierarchy-cell"]

My request is to have a configuration option that enforces that same behavior for specific columns as:

1. Add a "reorderable" flag to be set as part of the column configuration (set it to false for those we want to keep in place)

2. This flag will set a class on those columns the same way it works for columns with "k-group-cell" or "k-hierarchy-cell" classes, so the event can be prevented.

There is one important caveat to consider with this approach: Only columns at the front and the back of the grid can be locked in place, so there needs to be validation to prevent having non-reorderable columns among reorderable ones.