Please extend the comments feature so that it is broader than the limited focus of per record comments. Enhanced Collaborative Communication: By allowing comments at different levels, team members can have more context-specific discussions. This feature would enable users to leave comments on a specific base, table, or view, fostering clearer, more organized communication. It would essentially turn Airtable into a more collaborative workspace, where team members can easily discuss broader strategies at the base level, specific data sets at the table level, and particular views or filters. Improved Workflow Management: This feature would be a game changer for project management. Teams could streamline their workflow by discussing and tracking changes directly within Airtable, reducing the need for external communication tools. This centralized communication would lead to fewer misunderstandings and a more cohesive workflow, especially in remote or hybrid work environments. User-Friendly Experience: Embedding comments at different levels would make Airtable more intuitive and user-friendly. Users could easily navigate to relevant discussions without having to sift through unrelated comments at the record level. This is particularly beneficial for new team members who need to quickly understand the context and history of a project. Comments at the view level strike me as being the most useful - views are where most work is taking place and being able to have focused discussions at that level next to the data would be incredibly useful.  ... View more

What is the proposed idea/solution? Increase the functionality of the new form builder so that when the form is submitted the user is redirected to another URL. How does is solve the user problems? We use this on our new website to redirect the user to a form submitted page so that we can track conversations in Google Analytics. How was this validated? Greater control over where a user is directed post form submission. Who is the target audience? Web dev's and website users. ... View more

I have a database of members of an organisation and I from time to time I do an information check where I email them (using SendGrid) and ask them to confirm the information or reply with any edits. In its current format they have to reply to the email with any changes, or just to confirm. My request would be to be able to include buttons in the outgoing email that they can use to confirm. The button they click will then populate a Single Select style field in the original table. If they select 'No' however then they would have an option to list any corrections that would then populate in a Long Text style field in the original table. I would then be able to Group using that particular field so I would always be able to see who has and who has not replied. ... View more

So we are trying to move to Airtable for our project management system and specifically use the Gantt views. For context, we have been using Instagantt up to this point. However while testing I've noticed a bit of a deal breaking problem for us. For some reason, a dependent task can't start on the same day it's parent task ends. It shows as a conflict on the Gantt chart, and if you try to move either of the tasks, the chart will automatically push that task to start the day after it's parent ends. This is highly frustrating as we often have one day tasks, or tasks that need to start on the same day the proceeding tasks ends. I understand we can enter these in as milestones, but then our Gantt just has a bunch of milestones stacked up on the same day and it looks like crap. Instagantt and other Gantt charting software I have used has no problem being able to do this. I have included an example of one of our current projects from Instagantt. As it stands, the Gantt functionality is largely un-usable for us. I've seen this question asked a couple times before in other forms, but it seems several problems could be solved, and the general usability of this view type would be drastically improved if it would just support DateTime objects instead of just Date objects. In the attached example, the "Schedule" task has a "Work End" DateTime value of 11/14/23 0100, and it's dependent "Perform" task has a "Work Start" DateTime an hour later at 0200. These should NOT be conflicts, however they are still registering as such! This honestly feels like a bit of a design oversight as opposed to a decision (I'm hoping). At the very least, I feel the conflict checker logic needs to be updated from Child Start > Parent End to Child Start >= Parent End, as it is in most other popular Gantt platforms. The Calendar and Timeline views seem to handle DateTime's without issue, is there any plans to add this functionality to Gantts? ... View more

The issue is that in interfaces, the search feature hides rows of data that do not contain the keyword you are searching for in a grid view. This limits your ability to search and compare all rows of data.    This feature is possible when you use the search function in a data table but not in an interface.   ... View more

Views are useful, but sometimes a view needs to have lots of information in it regardless to be useful. Side scrollling with dozens of columns can be unwieldy and difficult to navigate (especially as the user adds new columns in different views, and they automatically place them at the end of other views). Colour coding and/or being able to group columns would seemingly be a simple to implement and very useful functionality. Grouping columns would be nice for tabbing between views and being able to move a bunch of columns at once (or unhide a column and have it snap to it's "group"). ... View more

What is the proposed idea/solution? Feedback from a UX perspective: It would be really helpful if there was a menu item on each base that takes the user to the base’s workspace.  How does is solve the user problems? It would save me time from going back home and scrolling through all of my workspaces to get to another base within the same workspace How was this validated? Experience; it would help all users ... ... View more

What is the proposed idea/solution? For film production, we need the ability to sum durations that are 24 frames per second.  HOURS:MINUTES:SECONDS:FRAMES With the current 00:00:00 format, it does not calculate accurately.    ... How does is solve the user problems? With the current duration formatting we can come close, but not be exact when summing TRT from multiple fields. A timecode format would allow accurate calculations.  ... How was this validated? Currently there's no way to tell AT that after 24 frames it's a new second. ... Who is the target audience? film production and editorial users   ... ... View more

What is the proposed idea/solution? This will help me to create a full duplicate of a table to another based with or without the data... How does is solve the user problems? Having to copy and pause the table details and have to relabel form questions ... ... ... View more