HOW DO I CREATE A SINGLE SELECT STATUS OPTION FOR EACH SUBTASK

Do you mean that Status dropdown should be dynamic depending on the task?

If so, you’ll want to have the following tables:

Task Templates

Status Options

Link the above tables, and have individual records for Status Options, linked to the corresponding Task Template.

Now, on your regular Tasks table you;ll want to have a link to Tasks Templates, and to Status Options.
Status Options will work as if it were a “single select” field type.

Then you’ll want to apply dynamic filters to your Status Options linked record, to make sure that it will only show those statuses linked to the template tasks through the Status Options table.
 

I know this was not super detailed, but I hope it helps. I’ll try to get back to it tomorrow!

Feel free to schedule a brief call if you’d like us to go through this together on the spot. Happy to help out.

Mike, Consultant @ Automatic Nation

Hmm, could you provide a screenshot example of your data and the end result? What’s an example of a ‘dedicated status option’?  

If each of the subtasks needs to have their own data associated to it (i.e. the status), then you’re probably going to need a table where each record represents a single subtask

How are you deciding who gets what subtask?  

Thanks for the responses, really appreciated.

To clarify, my case currently has a parent task, with an option for subtasks.

I also have  columns for status and allocation BUT these column only link to the parent task.

Hence for example:

Parent Task is: New Client

Subtasks are : 1) open file; 2) send into mai;l 3) send invoice .

The subtasks are handled by different persons on my team, hence each will have different status updates.

Presently i can only all8cate the parent task and not subtasks. Same applies for status.

I need to allocate each subtask to a different team member and each team member must be able to update the status of their respective task

My difficulty is that I can only as

Lots of different ways to build this, but one question that both Adam and Mike are trying to get at is Are you using 1 table for both Tasks and Subtasks?

If you’re using one table with a Parent/Child relationship between tasks and subtasks, you could of course add new columns only for the subtasks (Subtask Status & Subtask Assignment), perhaps with a different interface or view so they don’t get confused with the overtask. 

The other option is to utilize multiple tables, with linked record fields between them. so you have a Task table, and a Subtask table which are linked together. Depending on how consistent your Tasks are, you could set up automations to automatically create the relevant subtasks too. 

Here’s a SS of the single table solution 

Thanks, it's a single table.

The setup is a drop down multiple select for each subtask- reason is I have about 30 daily parent  tasks with a minimum of 2 subtasks.Having each subtask as a separate line item would leave me with a minimum of 90 line tasks which will be hard to work with.

Would a separate subtask and linking help me achieve what I require 

Yeah, the subtasks need to become data objects that can have their own attributes.

If you want to keep it in the same table but not have it be overwhelming, you could create views or groupings to make the information digestible, but really creating a subtasks table with linked records would probably be best.

I’d create a subtasks table with a formula field as it's primary field and include a single select with your subtask types. Write the formula field to combine the Parent Task Reference field from this table with the Subtask type so the record titles end up like “Nag 009 - CE”, “Nag 009 - ATT”, etc. Then you can assign different collaborators different subtasks and they can have different status.

For an example of this in action, if you look at the pre-built “Project Management” template, it works similarly.