Feature Requests

This is a broad use case I am struggling to find a solution for, if there is an existing answer please let me know. I want to be able to have sub tasks or deliverables on my action items, with the parent item completion and duration being derived from the child tasks. Bonus points if the child items can have their own dependencies amongst themselves, which then flow up to the parent as well. This is a big and abstract ask so I'll give an example. Task A, 5 hour duration, blocking task B Task B, contains sub tasks, blocking task C Task B1, 1 hr duration, blocking B2 Task B2, 2 hr duration, blocking B3 Task B3, 1 hr duration Task C, 2 hr duration I want Task B in the above example to automatically calculate a duration of 4hrs. Would also be amazing if each sub task status being completed would update the parent percent complete field, in this case marking Task B1 complete would change Task B to be 25% complete. Methods I have tried that did not work well: Checkbox Field - This has date and owner fields, but cannot have duration or dependencies. Suitable for reminders or short steps, but not useful for larger or complicated progress tracking. Sub Items - You can add duration and status to sub items, but you cannot set dependencies. I would be willing to forgo sub dependencies (since you can assume all sub tasks are blocking the parent task) but there is no linked duration or due dates. While you can do a rollup to get remaining duration for sub tasks you cannot dynamically update the duration field, and the formula field is unable to be formatted as a duration so a manual sum of child durations does not work either. Linked Record - I can make a separate table for sub tasks and link them all back to the parent, but it lacks the dynamic duration of the previous point as well as no way to link dependency at all between tables. I tried saying Task B is waiting for B1 etc, but I could not find a way to get the dependencies to link. The main tasks will only link to main tasks, and sub tasks will only link to sub tasks. Task Category - This is what I might end up going with even though I hate it. Basically, the entire table would be sub tasks with a single select used to group them by parent task. So I would have Task A1 with parent Task A, Task B1 Task B2 and B3 with parent Task B, etc. This way you can at least filter and group by the parent, but it is so clunky and requires manually linking the first and last sub task with the correct sub task of leading/following parent task. In this case, B3 needs to be set to be blocking C1, but if you add B4 then you have to go update the dependencies manually. I hope this text wall makes sense, and if anyone has a good solution to this please let me know!

Hey. I have a suggestion that I believe more people would appreciate. I am working with risk management that I want to record in multiple Solutions. My idea is that the "Risk" table (app) would be primarily in the "Risk Management" solution, but I could directly display this table as a table in the "Projects" or "Orders" solutions. I know that this can be solved with Linked Record within record, possibly in the dashboard, but it would be useful to display the table (with the possibility to set a filter) also as one of the tables (Apps).

It would be very useful to have a function that allows us to block/cancel creating or editing from a grid view, thus forcing the user to open the pop-up window, with this we could control dependent and mandatory fields (because editing from the grid the mandatory field is not respects) showing the sections depending on some field. I don't know if something similar already exists, but it would be excellent if we cannot control fields depending on other fields, that you could control that they do not modify from the grid to control the sections depending on conditionals.

Include dependencies (predecessors and/or successors) inside subtasks, and also the earliest and latest dates of the subtasks should define the timeline of the grouped task.

Prevent a record from being created, by requiring an entry to be unique, when the primary field is set to Auto Generated. Possibly giving you an error saying you need to change a value/values in a field/fields that are used for the auto-generation of the primary field.

Create an option to restrict data entry based upon data that has been entered into the record. My example: We track time spent on a task using a ["Date/Time" IN] field and a ["Date/Time" OUT] field. Sometimes our contractors are not diligent in entering these so an entry that should be Time IN - 11/01/24 09:00 AM and Time OUT - 11/01/24 10:30 AM is accidentally entered as Time OUT: 11/11/24 10:30 AM. This results in several hundred hours being tallied. I need 2 restrictions: Time OUT cannot be negative and Time OUT cannot be >10 hours.

When choosing records from a list for a fields such as linked records, you have a uniform way of filtering the choices using the cog icon, and that filter is then saved. For dependencies, the filtering is less powerful and I dont understand why. We only get "All statuses" or only records that aren't complete. No ability to filter out cancelled tasks for instance, or choose two statuses. Also I can't see how to change the display format for the list of records presented as options. For linked records fields, you can choose how the choices are presented, including what fields are shown within the box, but this doesn't seem possible for dependencies. Again, I dont understand why a different UX has been used instead of just using the same one used everywhere else. Thanks in advance for your help. Im transitioning over from Coda and while Im appreciating not having to make so many of the features I want myself, I'm missing flexibility and control Coda offers to users.

For now we do get the same popup (Are you sure) message when deleting fields with or without dependencies. As a first step, just updating the message to let the user know if there are any dependencies or not, and then being assisted to find and resolve the dependencies would be great!

Dependency fields are becoming super hard to use for project management with repeating task names (e.g. construction companies with the same number of tasks and same task names). Right now the only option to filter are by status or assigned to, which is completely useless if you have like many tasks especially when their names are repeating. Dynamic filtering like in other field types would help enourmosly to improve dependency fields. Otherwise the whole idea of project planning with Gantt charts becomes super hard to use. Another improvement that is necessary for this function is the ability to include dependencies in automations. That way it's much easier to streamline project planning and eliminate manual work and of course errors that can occur.

Example: You have full name field but split into sub fields (first name, last name, etc). Have ability to edit the sub field and sync with full name field. Same for other fields that have sub fields. This will also help a lot when copying data from other sources that are already split up in the other source.