Feature Requests

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.

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.

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.

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.

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.

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.

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.

Add Kuwaiti Dinar KD and Jordanian Dinar JD