Hi @preeyanka, thanks for reading and the interest in more structure around comments, glad to expand my thoughts to help you guys work on this! And yes I will send you a DM next week to connect on this, eager to discuss and it would be absolutely huge for my team’s efforts to adopt Coda fully if some of this stuff could wind up in production on Coda soon!
- Re: Resolved comments in their current set up. Yes, I think I have familiarized myself with their behavior as currently implemented. I think it would be useful if the resolved comments had a more natural presentation. I think the way the “disappear” when you click “resolve,” if you are using the default “comments only” view of comments is not as smooth at it could be. Also, to my point about the traceability of the resolution, what about a way to add a comment when resolving as I was suggesting, then have a notation in the comments that would indicate that this comment was the resolution. You guys currently notate with Marked as resolved, in the gray italics:
perhaps you could add near that an actual comment that closed the string. Then these threads can live almost as mini-tasks with conclusions, which I think would be very useful.
Here is a screenshot from Twist, a Slack alternative my team uses due to the ability to have substance around chatting, which is basically what I think would be useful in Coda: Instead of just one long stream of comments that can get unwieldy and out of context, comments are in threads that “close” in such a way that the person resolving can write the outcome.
To your question about controlling this feature, I think it would be great if you guys, via settings, could let the user determine if there has to be a comment along with a resolution, or not. Some teams may not want this overhead. A lot of other apps like Jira give you the option to “force” a pop-up modal when an issue is closed, for example, and enter a comment, which I think is a great feature.
And re: “Assigned Comments,” I am hopeful that you guys will come out with some kind of user dashboard, that, for example, will show a given team member all tasks assigned, sortable, and “assigned” comments would also be here. This could also serve as a sort of reminder function as you touched on. So you could see in one view work you need to do, such as the example of “could you complete the description of this task?” There might be some potential to have a type of Approval Flow as well - if a comment was sent to another team member who needed to approve, the other team member could come in, resolve, and then the task can move along. Even better would be if you could put in some control to say block the task from moving on its workflow until this comment was resolved, but that may be something we need to wait for even more advanced automations until you guys get to
I don’t mean to overwhelm, but I would really like to see the ability for a column type to be “comments,” and if you add to another row’s comments via a LookUp row, that would get noted in the comment string. This would save my team a ton of double entry when referencing rows during meetings and other situations. If you had the latest comment visible in the row, this could also help with rows that are representing team projects. The most recent comment sort of serves as the latest project update, so this is very useful when viewing in a table view multiple projects at once. This also is a feature I have never seen in any other app out there, but I believe it would be very well received by our Coda userbase, and provide you guys with one of your most unique features. You already have the ability to comment in a row simply by right clicking without the need to open the row - great work with this . Saving that extra click is a huge timesaver.
Finally, I would like to propose another feature of comments that may be out of place as it’s not related to resolving - the ability to pick which order the comments sort - either newest at the top, or oldest. A lot of apps give this option, and it’s very useful as some teams like to see the newest at the top, others at the bottom.
Thank you again for your interest in adding some of this to your guys’ upcoming comments iteration, and I will be in touch re: talking directly!