I’m curious about that design choice. Is there a reason why we can resolve inline comments but not comments in the entity comments field?
2 Likes
I was wondering the same thing! Linear has a great design solution for solving specific comments inside a card. It’s great because it’s very common to have more than one discussion inside an entity.
It can become very messy if we can’t mark as resolver specific threads in comments.
1 Like
Just not implemented.
Out of interest, what would you expect to happen to a comment thread that was resolved - would it be gone forever, or somehow hidden but findable?
Hidden but findable. If this is on the roadmap for the future, I recommend making resolving entity comments a per-database option.
I implement a consistent framework in database tools where comments are ethereal and meant to be resolved. Everything that should be permanent, or that has resilient context (which I define as not being only relevant for a short time) should be documented in the rich text or notes field.
In a task database, some comments are only relevant at a specific date and time in the process. These should be resolved as the discussion is resolved.
However, in a Subscriptions database, a comments field could be used for time-logging updates such as upcoming price changes, noting who the new admin is etc. These comments can be permanent. (Personally, I avoid using comments this way in Fibery because of how they are a page section that can grow infinitely long. Maybe if we could move comments to the sidebar…)
2 Likes