Skip to main content

[SOLVED] Simple checklist within fields


Forum|alt.badge.img+4

This would go a long way in letting many of us move completely away from Trello, Asana, Etc. into Airtable. I know there are workarounds (link to another table’s list containing the tasks), but that quickly becomes overly cumbersome. Would love to have simple checklist as a field option!

75 replies

Forum|alt.badge.img+4
  • Known Participant
  • 92 replies
  • January 3, 2018

I agree. I’ve been linking to a “task” table but it’s become cumbersome


YES! I am so happy to see that I am not the only person who has requested this. 95% of my tasks have some sort of 2+ step process. In order to make sure I do each step, a checklist is vital. Right now, since switching to AirTable I’ve moved all of my checklists to Evernote, then link to them from the AirTable record. It’s cumbersome and not ideal. When I used both Asana, Trello, and other proj mgmt systems they all had this feature… it was key for me. Lack of this feature was almost a deal-breaker for me when I switched to AirTable because checklists in tasks were integrated into the majority of what my team and I do every day. It also helps with QC to have the checklist within AirTable - if my team member assigned to a record checks all of the boxes, they are then held accountable for completing each step. Without that checklist where they have to check the box, they more frequently forget steps.


Forum|alt.badge.img+4

I’ve written a couple of blog posts which may help you with this subject - one with Airtable creating subtasks automatically and the other linking to Process Street which is a great app for standardising processes with repeatable tasks (and integrates well with Airtable):

Using Airtable / Zapier to create checklists:

http://software.kirknessassociates.com/blog_files/3071ed2bbea12791bdd3eab57ff09fcd-20.html

Using Airtable and Process Street:

http://software.kirknessassociates.com/blog_files/11a79a74e2d3f3672f5d0c40fa251ff4-24.html


Forum|alt.badge.img+12
  • Known Participant
  • 23 replies
  • January 6, 2018

+1 on ditching Trello and similar apps once this is implemented!


Ricardo11
Forum|alt.badge.img+14
  • Inspiring
  • 50 replies
  • January 13, 2018

+1 would love switch from Trello to Airtable, check list and more sophisticated formatting are keeping me!


Forum|alt.badge.img+4

I’ve already commented on this once but I thought I would add some comments further…

Personally, I would vote against adding a special task list field type to Airtable (or any other relational database for that matter) as it is too inflexible and generally bad practice. For me, the correct way to implement this in a database is to use a tasks table as @Hashim_Warren says above. The problem is that Airtable’s UI implementation makes this cumbersome (it’s a bit better in Expanded view).

A better solution, and one that would be far more general purpose would be for Airtable to implement a better solution in their UI for using child tables - and importantly, to also enforce referential integrity properly - for example, to make sure that one to many relationships are enforced no matter how a record is entered and provide for Cascade Delete to remove child records when the ‘parent’ is deleted.

This isn’t top of my priority list but it’s up there - having said that Airtable is a great product to use!


  • New Participant
  • 3 replies
  • January 25, 2018
Julian_Kirkness wrote:

I’ve already commented on this once but I thought I would add some comments further…

Personally, I would vote against adding a special task list field type to Airtable (or any other relational database for that matter) as it is too inflexible and generally bad practice. For me, the correct way to implement this in a database is to use a tasks table as @Hashim_Warren says above. The problem is that Airtable’s UI implementation makes this cumbersome (it’s a bit better in Expanded view).

A better solution, and one that would be far more general purpose would be for Airtable to implement a better solution in their UI for using child tables - and importantly, to also enforce referential integrity properly - for example, to make sure that one to many relationships are enforced no matter how a record is entered and provide for Cascade Delete to remove child records when the ‘parent’ is deleted.

This isn’t top of my priority list but it’s up there - having said that Airtable is a great product to use!


also @Hashim_Warren provide an example of how’d you’d structure the main and “task” tables. I have one done but it can’t be optimal. My main table has a one-to-many relationship to the task table. The main table checklist column displays no tasks if all are complete and vice-versa displays all tasks if none are complete. Please tell me this isn’t the best way to do this currently.


Forum|alt.badge.img+4
Adam_Acosta wrote:

also @Hashim_Warren provide an example of how’d you’d structure the main and “task” tables. I have one done but it can’t be optimal. My main table has a one-to-many relationship to the task table. The main table checklist column displays no tasks if all are complete and vice-versa displays all tasks if none are complete. Please tell me this isn’t the best way to do this currently.


Hi Adam

What you’ve done sounds correct to me - are you able to provide screen shots of each table to confirm?


  • New Participant
  • 3 replies
  • January 25, 2018
Julian_Kirkness wrote:

Hi Adam

What you’ve done sounds correct to me - are you able to provide screen shots of each table to confirm?


Sorry I don’t feel comfortable doing that. Thank you for reaching out Julian. I appreciate it very much. I’m going to try to use a third table for now and see how that goes.


Forum|alt.badge.img+4
Adam_Acosta wrote:

Sorry I don’t feel comfortable doing that. Thank you for reaching out Julian. I appreciate it very much. I’m going to try to use a third table for now and see how that goes.


No problem!

If you do get stuck then create a copy of your base and randomise the data with some copy and pasting (or delete it and enter a few records) and I’ll take a look.


Forum|alt.badge.img+10
  • Known Participant
  • 19 replies
  • February 16, 2018
Julian_Kirkness wrote:

I’ve already commented on this once but I thought I would add some comments further…

Personally, I would vote against adding a special task list field type to Airtable (or any other relational database for that matter) as it is too inflexible and generally bad practice. For me, the correct way to implement this in a database is to use a tasks table as @Hashim_Warren says above. The problem is that Airtable’s UI implementation makes this cumbersome (it’s a bit better in Expanded view).

A better solution, and one that would be far more general purpose would be for Airtable to implement a better solution in their UI for using child tables - and importantly, to also enforce referential integrity properly - for example, to make sure that one to many relationships are enforced no matter how a record is entered and provide for Cascade Delete to remove child records when the ‘parent’ is deleted.

This isn’t top of my priority list but it’s up there - having said that Airtable is a great product to use!


This feature request is not for a special task list field type, but for the ability to put a simple checklist in a field. Subtasks should be handled using relational mechanisms as you note, but that is a “heavyweight” solution for a simple checklist: think instead a rich text field that allows checkboxes and/or tables with a list of things to be done within a single assigned task, and maybe some notes for each step. The checklist is just text as far as Airtable is concerned. The value to this is that I don’t have to clutter my task list to track the task list items, I don’t have to keep the checklist in a separate document as I currently do, and I don’t have to write ad hoc notes to track work done on standard multi-part tasks.


Forum|alt.badge.img+4
David_Isaac wrote:

This feature request is not for a special task list field type, but for the ability to put a simple checklist in a field. Subtasks should be handled using relational mechanisms as you note, but that is a “heavyweight” solution for a simple checklist: think instead a rich text field that allows checkboxes and/or tables with a list of things to be done within a single assigned task, and maybe some notes for each step. The checklist is just text as far as Airtable is concerned. The value to this is that I don’t have to clutter my task list to track the task list items, I don’t have to keep the checklist in a separate document as I currently do, and I don’t have to write ad hoc notes to track work done on standard multi-part tasks.


Hi David

OK - I’ll go with you on this - even as far as a simple checklist field type - after all it’s really just a different UI for a multi select field. (In fact it could simply be an option for a multi select field).

What I would really like, though, is a better UI for one to many relationships so that using them is more intuitive.


Forum|alt.badge.img+10
  • Known Participant
  • 19 replies
  • March 15, 2018
Julian_Kirkness wrote:

Hi David

OK - I’ll go with you on this - even as far as a simple checklist field type - after all it’s really just a different UI for a multi select field. (In fact it could simply be an option for a multi select field).

What I would really like, though, is a better UI for one to many relationships so that using them is more intuitive.


Julian-
I’m with you on the need for an intuitive UI for one-to-many relationships…thanks for upvoting my feature request (Split-screen master-detail record view).

I also like your idea about a checklist format for a multi-select list, but this doesn’t replace the need for a simple checklist within fields, because I want different records in the same table to have different checklists.

Also, for the benefit of anyone from Airtable that might review this, I want to reiterate that a rich-text table would be awesome, because I could have additional information for each checklist item (e.g., brief notes for each). I have a bunch of real-world use cases. For example, test steps within a testcase record (with step number, checkmark, expected results, actual results for each step). Each testcase is either done or not done, but the tester needs to track the steps. Similar idea for administrative tasks: the task is either done or not done, but some tasks have several small steps I want to check off and make notes on.


I agree with this thread. Right now I’m considering migrating over to AirTable from Wunderlist. Except Wunderlist has drop dead simple sub tasks. I get the fact that a column type for subtask is extremely un-elegant.

But there needs to be a solution. I’m fine if under the covers the cell (or column) becomes backed by a shadow table. But this is a stupid-simple requirement for me to migrate over from wunderlist. I’m disappointed this isn’t here.


  • New Participant
  • 1 reply
  • April 3, 2018

Please oh please create a simpler and nice looking way to create checklist items. This is imperative to project workflow. Honestly the only thing keeping me from fully going Airtable rather than Trello. I have used the cumbersome link to checklist and it is horrible for so many reasons.

1.Everything you place in the linked checklist tab ends up in reverse order on the checklist column, so you have to go back in and flip them all back around. This has to be done from the Expand Record box…they don’t talk to each other after they are created. Which means I now have to maintain 2 checklists for each record.
2. If you hide checked items on the tab, it does not fall off the column.
3. If you want to check the item off from the column it takes 5 clicks…2 of which are unnecessary. Wish you could click the box on the Expand Record screen.
4. Checklists in the column or in the expand record screen are not formatted well, rendering them useless.

There are probably more, but that is enough to make me not want to use this.


  • New Participant
  • 1 reply
  • April 10, 2018

What works well for us is creating a multiselect field. We then start with all of the items in the multiselect selected and then remove them as they are completed. Works well actually. We just have a row at the top of the table that we use as a template and duplicate it so we don’t have to select all of the items for each new item.


Forum|alt.badge.img+18
Torey_Maerz wrote:

What works well for us is creating a multiselect field. We then start with all of the items in the multiselect selected and then remove them as they are completed. Works well actually. We just have a row at the top of the table that we use as a template and duplicate it so we don’t have to select all of the items for each new item.


@Torey_Maerz - that’s a great idea for tables that require the same checklist for every record! Thanks for sharing.

However, it still doesn’t solve some people’s problem if they want to have a unique checklist for each record. Your solution could be extended to having all the possible checklist items they want in the multi-select field, and then adding the ones they need to use. But I imagine for some people, this would end up being an infinitely growing list of multi-select options.

Still, thanks for the suggestion - I may use this for a couple issue’s I’ve been trying to get around!


  • New Participant
  • 1 reply
  • April 12, 2018

This would be EXTREMELY helpful. Totally agree. Ready to switch over completely from Trello/Asana


  • Participating Frequently
  • 5 replies
  • April 20, 2018

I think that maybe airtable is not designed for this kinda thing. I look at it more as an overview, project mgmt deal and not task mgmt. I’m going to look into integrating with process street. the only suggestion i have is to list out your tasks in a table, then link to another field (projects) and then group the tasks via project. that way you’ll be able to see your tasks under each project and also you can click the header in the due field (is this the right word) and then you can see the percentage of the tasks that have been done.

I hope this helps.


+1 for this option to move away from Trello. Can’t wait to see it.


+1 for simple, ad-hoc To-Do/checklists within an airtable entry. These do not need to be relational – nor sure they be. Ditto on the use case from from moving over from Trello…


Came here because I was looking for a solution - we’ve used Axosoft up until now for project management, and it does a great job of having sub-issues which you can expand/collapse from the parent issue.

I found a workaround in Airtable that works really well for us - may be hard to explain, but here goes:

  • The primary field in our table is called “Sub-Task” - this is the granular level task that needs working on.
  • I then have a field next to it called “Parent Task”. This is an optional field, as I’ll explain below.
  • I then Group By “Parent Task”, which has the effect of separating out all Parent Tasks into their own section. Any sub-tasks that don’t have a parent task are just collected together in their own “Empty” group.
  • Each parent task’s Group can then be expanded/collapsed to view all sub-tasks. And it shows a count of how many sub-tasks there are in each parent task, which is handy.
  • You can then group further by Category or Person (set this grouping before Parent Task), so you could see all “Features” tasks as one group, and inside that would be all Parent Tasks, and then expand each parent task to view sub-tasks.
  • I added a “Completed” checkbox for each sub-task, and then set the Group summary for the Completed field as “Percent Checked” - this shows us % progress for the parent task (and any Grouping above/below that), even when collapsed.
  • Finally, I created a couple of duplicate views, so I can see “All tasks, grouped by Category” (e.g. marketing vs. Features vs. Business), then one for “Tasks per person”, one for “What each person is currently working on” (Group by “Assigned To”, then Group by “Parent Task”, Filter where Progress = “In Progress”), and “My current tasks” (Filter where Progress = “In Progress”, Assigned to = me).

Another benefit is that any single task can easily be turned into a task with sub-tasks, simply by typing something into the “Parent Task” field. Airtable automatically moves it to its own group, where you can then add lots of new rows and type each sub-issue into the “Sub-Task” field.
Added bonus - you can create lots of sub-tasks really quickly. Type all of your sub-tasks into a plain text document, one task on each row - copy to clipboard. Then click in a blank Sub-Task field, and paste. It will ask if you want to Expand the Group by default - that option then creates a separate sub-task for each line of your pasted text.
Thus, the workflow to create a parent task with 10 sub-tasks is super-easy:

  • create a new row, and type something as the Parent Task name
  • grab 10 plain text lines and paste them into the Sub-Task field.
  • Done.

I’ve only just set this up, so will have to see how this works over the long run, but straight away it feels like I have a way of managing my tasks, people, and progress, better than any other tool.

Here’s an example of how it looks:

Unlike Axosoft, which I chose because it’s powerful, the UI in Airtable is easier to use, and seems more flexible, especially with different field types and Views.

Hope that helps anyone trying to manage sub-tasks too!


Forum|alt.badge.img+10
Claude_Schneide wrote:

Came here because I was looking for a solution - we’ve used Axosoft up until now for project management, and it does a great job of having sub-issues which you can expand/collapse from the parent issue.

I found a workaround in Airtable that works really well for us - may be hard to explain, but here goes:

  • The primary field in our table is called “Sub-Task” - this is the granular level task that needs working on.
  • I then have a field next to it called “Parent Task”. This is an optional field, as I’ll explain below.
  • I then Group By “Parent Task”, which has the effect of separating out all Parent Tasks into their own section. Any sub-tasks that don’t have a parent task are just collected together in their own “Empty” group.
  • Each parent task’s Group can then be expanded/collapsed to view all sub-tasks. And it shows a count of how many sub-tasks there are in each parent task, which is handy.
  • You can then group further by Category or Person (set this grouping before Parent Task), so you could see all “Features” tasks as one group, and inside that would be all Parent Tasks, and then expand each parent task to view sub-tasks.
  • I added a “Completed” checkbox for each sub-task, and then set the Group summary for the Completed field as “Percent Checked” - this shows us % progress for the parent task (and any Grouping above/below that), even when collapsed.
  • Finally, I created a couple of duplicate views, so I can see “All tasks, grouped by Category” (e.g. marketing vs. Features vs. Business), then one for “Tasks per person”, one for “What each person is currently working on” (Group by “Assigned To”, then Group by “Parent Task”, Filter where Progress = “In Progress”), and “My current tasks” (Filter where Progress = “In Progress”, Assigned to = me).

Another benefit is that any single task can easily be turned into a task with sub-tasks, simply by typing something into the “Parent Task” field. Airtable automatically moves it to its own group, where you can then add lots of new rows and type each sub-issue into the “Sub-Task” field.
Added bonus - you can create lots of sub-tasks really quickly. Type all of your sub-tasks into a plain text document, one task on each row - copy to clipboard. Then click in a blank Sub-Task field, and paste. It will ask if you want to Expand the Group by default - that option then creates a separate sub-task for each line of your pasted text.
Thus, the workflow to create a parent task with 10 sub-tasks is super-easy:

  • create a new row, and type something as the Parent Task name
  • grab 10 plain text lines and paste them into the Sub-Task field.
  • Done.

I’ve only just set this up, so will have to see how this works over the long run, but straight away it feels like I have a way of managing my tasks, people, and progress, better than any other tool.

Here’s an example of how it looks:

Unlike Axosoft, which I chose because it’s powerful, the UI in Airtable is easier to use, and seems more flexible, especially with different field types and Views.

Hope that helps anyone trying to manage sub-tasks too!


Thanks for this work around Claude! It really helped.


I hope there’s an update for this. Would be great to have multiple checklist within a field. That would make things so so much easier.


  • New Participant
  • 2 replies
  • June 6, 2018
Claude_Schneide wrote:

Came here because I was looking for a solution - we’ve used Axosoft up until now for project management, and it does a great job of having sub-issues which you can expand/collapse from the parent issue.

I found a workaround in Airtable that works really well for us - may be hard to explain, but here goes:

  • The primary field in our table is called “Sub-Task” - this is the granular level task that needs working on.
  • I then have a field next to it called “Parent Task”. This is an optional field, as I’ll explain below.
  • I then Group By “Parent Task”, which has the effect of separating out all Parent Tasks into their own section. Any sub-tasks that don’t have a parent task are just collected together in their own “Empty” group.
  • Each parent task’s Group can then be expanded/collapsed to view all sub-tasks. And it shows a count of how many sub-tasks there are in each parent task, which is handy.
  • You can then group further by Category or Person (set this grouping before Parent Task), so you could see all “Features” tasks as one group, and inside that would be all Parent Tasks, and then expand each parent task to view sub-tasks.
  • I added a “Completed” checkbox for each sub-task, and then set the Group summary for the Completed field as “Percent Checked” - this shows us % progress for the parent task (and any Grouping above/below that), even when collapsed.
  • Finally, I created a couple of duplicate views, so I can see “All tasks, grouped by Category” (e.g. marketing vs. Features vs. Business), then one for “Tasks per person”, one for “What each person is currently working on” (Group by “Assigned To”, then Group by “Parent Task”, Filter where Progress = “In Progress”), and “My current tasks” (Filter where Progress = “In Progress”, Assigned to = me).

Another benefit is that any single task can easily be turned into a task with sub-tasks, simply by typing something into the “Parent Task” field. Airtable automatically moves it to its own group, where you can then add lots of new rows and type each sub-issue into the “Sub-Task” field.
Added bonus - you can create lots of sub-tasks really quickly. Type all of your sub-tasks into a plain text document, one task on each row - copy to clipboard. Then click in a blank Sub-Task field, and paste. It will ask if you want to Expand the Group by default - that option then creates a separate sub-task for each line of your pasted text.
Thus, the workflow to create a parent task with 10 sub-tasks is super-easy:

  • create a new row, and type something as the Parent Task name
  • grab 10 plain text lines and paste them into the Sub-Task field.
  • Done.

I’ve only just set this up, so will have to see how this works over the long run, but straight away it feels like I have a way of managing my tasks, people, and progress, better than any other tool.

Here’s an example of how it looks:

Unlike Axosoft, which I chose because it’s powerful, the UI in Airtable is easier to use, and seems more flexible, especially with different field types and Views.

Hope that helps anyone trying to manage sub-tasks too!


Thanks Claude - very Helpful

One disadvantage is that all “parented groups” of tasks will either be on the top or the bottom - but until Airtable adds it in - this is a good way to go


Reply