Kanban boards have always had a blind spot in Odoo. Group your pipeline by salesperson, by stage, by priority — and everything works exactly how you’d expect. You drag a card, it moves. You click the plus button, a new record appears in that column. But try grouping by a date field — expected close date, project deadline, delivery week — and the board goes read-only. Cards sit frozen in their columns. The quick-create button vanishes. You’re left staring at a nicely-organized view that you can’t actually interact with.
That limitation has quietly disappeared. Odoo’s kanban view now supports a new attribute called allow_group_range_value that unlocks drag-and-drop and quick-create for date-grouped boards. The change sounds incremental, but it fundamentally alters how teams can use kanban for forecasting, scheduling, and deadline management.
Why Date-Grouped Kanban Was Broken in the First Place
The original limitation wasn’t arbitrary. When you group a kanban board by a selection field like “Stage,” each column has a single, unambiguous value. Drag a deal from “Qualified” to “Proposal Sent” and the system knows exactly what value to write. But date grouping creates ranges — “January 8 to 14,” “January 15 to 21” — and a range isn’t a value. The system had no clean way to decide what date a record should get when you dropped it into a week-long bucket.
The workaround most teams landed on was predictable: don’t group by date in kanban. Use a list view, or a calendar, or a Gantt chart. The kanban board — despite being the most intuitive interface for visual pipeline management — was effectively off-limits for any workflow organized around time.
How the New Attribute Works Under the Hood
The solution hinges on a piece of infrastructure that was already in place but underutilized. When Odoo’s ORM groups records by a date or datetime field, its read_group method returns a __rangeproperty for each group. This property contains a half-open interval — a from date and a todate — that defines exactly which dates fall into that column. A weekly group for January 8 through 14 would carry a range of [2026-01-08, 2026-01-15), where the start is inclusive and the end is exclusive.
With allow_group_range_valueset to true on a kanban field element, the frontend now reads that range data and uses the final date of the interval as the value to assign. Drop a deal into the “Jan 8–14” column and its expected close date becomes January 14. Quick-create a task in the “Jan 15–21” column and the deadline is set to January 21. The system consistently picks the end of the range, which makes practical sense: if you’re slotting something into a week, the last day of that week is the most conservative deadline assumption.
The attribute defaults to false, which means existing kanban views behave exactly as they always have. Developers have to explicitly opt in for each field where date-based drag-and-drop makes sense. This is a deliberate design choice — not every date field should be overwritten when a card moves. An invoice date, for instance, should stay locked regardless of where someone drags the record.
Sales Forecasting Gets a Proper Visual Tool
The most obvious beneficiary is the CRM pipeline. Sales teams have long wanted to group their opportunities by expected close date and then shuffle deals between weeks as conversations progress or stall. Before this change, doing that required opening each record individually and manually editing the date field. Now, a sales manager can look at a kanban board grouped by week, see that a deal originally slated for this week isn’t going to close in time, and drag it to next week’s column in a single gesture. The expected close date adjusts automatically.
Quick-create becomes equally powerful in this context. A salesperson takes a call, qualifies a new lead, and wants to slot it into their forecast for two weeks from now. They click the plus icon on the target week’s column, type a name, and the opportunity is created with the right expected close date already filled in. No form navigation, no manual date picking, no mental arithmetic about which date falls in which week.
Project Management and Beyond
The applications extend well past sales. Project managers who organize tasks by deadline week can now drag cards to reschedule them. Marketing teams planning campaign launches across monthly buckets can rearrange their timeline visually. Manufacturing planners who group production orders by delivery week can shift priorities by moving cards between columns.
Any workflow where records have a meaningful date field and where visualizing those records in time-based buckets makes sense is now a candidate for interactive kanban. The constraint was never that people didn’t want to work this way — it was that the framework didn’t support it. The opt-in attribute removes the technical barrier without imposing the behavior on views where it wouldn’t be appropriate.
This pattern also opens up interesting possibilities for custom modules. A service company tracking contract renewal dates could build a kanban board grouped by renewal month and let account managers drag contracts forward as renewal conversations develop. A logistics team could group shipments by expected arrival week and visually manage their receiving schedule.
Part of the WOWL Frontend Evolution
The date-range kanban feature is part of Odoo’s broader WOWL — Web OWL — frontend framework evolution, which has been systematically rearchitecting how views handle data, interaction, and rendering. WOWL replaced the legacy JavaScript framework with OWL (Odoo Web Library), and each release has expanded what the new component-based architecture can do.
What makes this particular addition notable is that it solves a problem that existed in the old framework too but was never addressed. The legacy kanban had the same date-grouping limitation — cards couldn’t be dragged between date columns. Rather than simply replicating old behavior, the WOWL rewrite created an opportunity to fix long-standing interaction gaps, and the allow_group_range_value attribute is one of the results.
What This Means for Teams Using Odoo Today
For end users, the change is invisible until a developer or administrator enables it on a specific view. There’s no global toggle, no system setting to flip. Each kanban view definition must include the attribute on the relevant field element. This means the feature will roll out gradually as module maintainers add it to the views where it makes sense — CRM pipelines, project task boards, HR leave calendars, and so on.
For Odoo developers and studio users, the path is straightforward: add allow_group_range_value=“1”to the field element in your kanban view definition, and the board immediately gains drag-and-drop and quick-create when grouped by that date field. No Python changes, no server-side logic, no migration scripts. It’s a single XML attribute that unlocks an entirely new interaction model.
The gap between “I can see my data organized by time” and “I can manipulate my data organized by time” has always been the difference between a report and a tool. Odoo’s date-grouped kanban just crossed that line.