🔦 Feature: Different fields for "card" and "record" view in Kanban

[springfielddatarecovery]

Please confirm if feature request does NOT exist already ?

• [X] I confirm there is no existing issue for this

Describe the usecase for the feature

Kanban view enables grouping records by a specified column (such as "state" or "job status"). Each card shows a set number of user-configured fields. The cards provide a quick "at a glance" overview of records and their states.

However, when clicking a record to expose the 'record view', the same fields are shown. Ideally, this record view would contain more fields while the card view provides a more limited set, but NoCoDB does not support this differentiation yet.

Suggested Solution

Each Kanban view should have two sets of fields:

• Fields which show in the "card view"
• Fields which show in the "record" view

Additional Context

No response

[dstala]

Record view shows enabled fields by default. There is an option to show hidden fields.

Thought process here

• User has identified core fields to be displayed on card & these will be the one's user would constantly tinker with
• Hidden fields are still available for quick access, but needn't be shown by default always

[springfielddatarecovery]

I understand the idea of hiding them behind an additional layer (hidden fields). But this is one extra click for a user who wants to update a record. The Kanban card view provides a quick overview of records grouped by something (like job status), clicking on the record opens the record view (to modify the record). Right now, the only way you can have something show up in the record view is by also making it show up in the card view which means the cards can get large and unwieldy quickly.

There are fields a user may generally want to keep hidden even when in the edit view (those can go into "hidden fields"), and those are not the same as fields a user wants to keep hidden in the card view.

Other softwares which fill this "database with a frontend" niche often allow the user to customize field display in this way. Grist allows this, for example, as does Drupal.