Kanban View based on Lookup field - single Select or Collaborator


Continuing the discussion from Calendar View based on Lookup field dates:

Now that Lookup fields work for Calendar Views, please extend this functionality to Kanban View.

My use case…

I have a base that covers our video content management and review process. Three key tables and fields are:

  1. Table of Videos: Title, Description, etc.
  2. Table of Reviews, including fields for when the last review was, a formula for when the next review is due, and who will do the review.
  3. Table of Account users, including fields for people’s name, their role in video content management, email address, and a Collaborator field type named Airtable user. (Most, but not all of the team will have Airtable accounts.)

I’d like Kanban Views of Videos / Reviews stacked by the Lookup field which references a single Airtable user. Videos / Reviews kanbans would be stacked by each Airtable user assigned. Any Videos / Reviews assigned to team members who aren’t Airtable users would be listed in the Uncategorized stack.

Lookup field extension is a massive feature extension for Calendar Views. Let’s do likewise for Kanban! :smile:


I’d also like to use a lookup field as the grouping on a Kanban View.

I am using a base to manage a product roadmap. There’s a table of Features and another table of Release Dates (among other things). I’d love to use the Kanban View to group features by release date, given that it’s a single-select lookup field.

My workaround at the moment is to create a single-select dropdown that mimics the value of the lookup field.

Hope this is the best way to “vote”!


This. Please. I want to be able to Kanban view attendees by event.


I have a table listing locations, and another table listing site visits. One of the data points for a site visit is the location, and I want to create a Kanban view grouping my site visits by location. To do this, I’d need to get rid of my location table, and maintain the list of locations in the site visit table, and every other table that references location.

I see this was requested more than a year ago. Is it on the roadmap? Please let us know.


Literally. Begging. For. This. Capability.


Dragging in an entire bag of +1