+1 to the feature request!
Also, a suggestion for a hacky workaround (that I have implemented, and works ok). Basically, don’t use the comments section of the airtable records at all. Instead, do all commenting in a dedicated slack thread per record. Here’s what I did to make that work:
- any time a record is created, use zapier to automatically create a slack thread for the record, and place a link to that thread in a prominent field in the record. For fun, I also @ the creator of the record within the thread, and include a link back to the record. All these slack threads are in a single “airtable slack threads” channel.
- require (by policy) that all commenting happen in the slack thread. (people click the link, have the conversation in slack)
This has an interesting beneficial side effect, which is that you can easily add zapier automations to @ people in the thread for other changes to the record. For example, whenever the members field of a record changes, you can @ all members. (or the new members, if you’re extra fancy) You could potentially implement @'ing in other fields of the record as well. (e.g. if you had a checklist field and wanted to mention people on items, you could parse out the slack names using a custom zapier script, and @ those folks in the thread)
This general solution does require extra fields in the table, but the upside is that you don’t have to set it up for each person’s email.
