# Why can't we resolve entity comments?

**URL:** <https://community.fibery.io/t/why-cant-we-resolve-entity-comments/10039>\
**Category:** Ideas & Features\
**Tags:** comments\
**Created:** [November 19, 2025, 5:30pm UTC](https://community.fibery.io/t/why-cant-we-resolve-entity-comments/10039 "2025-11-19T17:30:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [November 19, 2025, 5:30pm UTC](https://community.fibery.io/t/why-cant-we-resolve-entity-comments/10039/1 "2025-11-19T17:30:35Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Renato\_Carvalho](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/renato_carvalho/32/11001_2.png) [@Renato\_Carvalho](https://community.fibery.io/u/Renato_Carvalho)\
**Post date:** [November 19, 2025, 10:21pm UTC](https://community.fibery.io/t/why-cant-we-resolve-entity-comments/10039/2 "2025-11-19T22:21:06Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [November 20, 2025, 2:39pm UTC](https://community.fibery.io/t/why-cant-we-resolve-entity-comments/10039/3 "2025-11-20T14:39:15Z")

</div>

> [@helloitse](#):
>
> Is there a reason why we can resolve inline comments but not comments in the entity comments field?

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?

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [November 20, 2025, 3:14pm UTC](https://community.fibery.io/t/why-cant-we-resolve-entity-comments/10039/4 "2025-11-20T15:14:41Z")

</div>

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…)