Kanban View based on Lookup field - single Select or Collaborator

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

Any progress on this? Add one more request to the list, please!

Any progress on this please?

+1 from me.

Lookup fields are critical to creating good normalised structure and the kanban view is a great way to visualise these into groups.

+1 as well, super interested in this feature, it’d allow us to have Trello like views, it’d be grand!

This would be great, and I’m not quite sure why we can’t do it? I have a linked field (actually from a synced base) that relies on a single select status field.

I do not want to double enter my statuses. I do need to keep my statuses up to date, as they’re the field I want to show to my developers so I can use this view to keep them on track for deliverables.

Does anyone have a workaround?

Maybe you can create an Automation that update the Kanban field from the Synced field.

Thank you! I should have closed the loop here. That’s exactly what I did. Here’s what I did:

This definitely works best with a paid version of airtable, because it requires syncs and automations, but I synced the original table with the statuses to the table with the kanban view.

(This part is probably extra, but I did it because I’m extra.) I made a linked record from the synced table to the table with the kanban view (they have an obvious relationship- records in both tables are the states of the United States and the District of Columbia). I added a look up field to that table with the status field. I also created a placeholder field for “status”- I only use it if for some reason there’s a problem with the automation, which there occasionally is.

Then I did created an automation- when the synced table’s status updates, the automation updates the status in the kanban view.

Hi Lauren
This sounds really useful.
I am trialing AirTable at the moment and would have the same requirement, but no idea how the automations work yet. Is there anything you can share?
I have Process stages the work flows through in a table and want these to be the KanBan statuses, but core functionality doesn’t seem to allow.
Thanks
Graham

The automation ended up working fine for this, but I can barely remember what I did anymore. I have a single-select status field that I never touch in the table with the kanban view (you can even lock it and make the editing permissions only available to automations). Then I adjust the statuses on the other table, which has a bunch of other stuff that’s irrelevant to my developers.

When we update the statuses on the table we use most of the time, the automation updates the status view that the developers need.

I hope that’s helpful!