Kanban grouping using link fields

I sort of found a work around for this. You can use the matrix block. Choose your real lookup field for the columns. Then choose a second lookup field for the rows that has the same value for every record in the table. In my case I made a new table called ‘Matrix’ and then added a Matrix field to my table.

The downside of this is that you can’t customize the cards. They only show the primary field.

+1 for kanban by link fields (when multiple selection is disabled)

Also, if you use a lookup field to look up the value of a single-value field in the linked table and the link is single-valued, the lookup field is effectively single-value, so it should be usable as a single-select field for a new kanban view.

Yes please and thank you.

+1 Yes PLEASE to single select, linked records that can be used in Kanban!!
I produce large-scale, live events. I create large contact sheets for the teams working on the project, all of whom I will not be inviting as collaborators on my project’s airtable. Without this, I cannot assign a task to a person on my contact sheet unless I’ve invited them to airtable as a collaborator.

Also looking for this feature.

+1 for this feature.

+1 This would be very valuable

Same here! Would love this option.

Adding my +1 as well.

My current workaround is to duplicate the Linked Record field and change it to a Single Select field. Then I can group the Kanban by that duplicated field

I need this too. It’s another limit pushing me away.

Any news on this?
For us this is must have

Hilarious. I just posted a very similar feature request — see my linked post below.

This is absolutely one of the biggest drawbacks & biggest limitations in using Airtable — yet it applies to ALL VIEWS, not just Kanban views!! It is a major problem with the entire Airtable platform, and I really wish that the Airtable engineers would prioritize this.

If I was an engineer working on Airtable, this would be my #1 priority.

Mark me down for an up vote too. It doesn’t really make sense to have the single select functionality, but not have single record linked tables as an option. Isn’t that the benefit of Airtables?

Try Matrix Block. It may work.

One more request for this feature. Please!

One more vote for this !

I’ve just created an account, and this is my first blocking issue.

In addition to this thought. I would also like to add the request to be able to actually ‘Group’ by columns, therefore creating multiple collapsable kanban’s in a single view if that makes sense.

For example if I have a linked column for ‘client or account’ the only way to come close to this functionality is use the filter method then that restricts me to 1) only seeing a single client at a time 2) remembering all clients to filter by 3) not being able to see where each clients tasks are in their kanban grouped on top of each other, if that makes sense? :slightly_smiling_face: Of course we can use the group method on a regular grid view to create a similar effect but it’s not exactly the same ‘kanban’ style experience.

Hope this helps!

+1 blocking issue for switching to this platform.

I need to allow users backend access their own user data through these views by filtering and grouping by username. I cannot believe that this capability is not available. Am i missing something here, are we suppose to use blocks or something else for this?

+1 for using Linked Fields in the Kanban View – Please help us Airtable!

Any development here @Airtable_Admin1 or others? This is really problematic as we have to maintain a “Single Select” duplicate of our Link to Records column which increases margin of error substantially. The main reason we use airtable over others is for the data relationships and removal of manual redundancy.

+1 to single select getting its data from a linked table. Kanban grouping would be the most obvious application, but I’m sure there would be others.

While you’re at it, if that “get” of the data from the linked table could be filtered based on the value of some column in the current table… that would make the general feature twice as useful. i.e. don’t show the data-enterer the values that aren’t relevant for the particular row they’re entering.

+1 for this functionality – This would be a game changer!

plus 1 here. I just started creating my first project based on a modified template and hit this limitation right away.