# Nov 2, 2023 / Collapse replies in entity comments, Fibery User Guide chatbot **URL:** \ **Category:** Changelog\ **Created:** [November 2, 2023, 12:08pm UTC](https://community.fibery.io/t/nov-2-2023-collapse-replies-in-entity-comments-fibery-user-guide-chatbot/5364 "2023-11-02T12:08:42Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [November 5, 2023, 4:47am UTC](https://community.fibery.io/t/nov-2-2023-collapse-replies-in-entity-comments-fibery-user-guide-chatbot/5364/11 "2023-11-05T04:47:28Z")
> [@antoniokov](#): > > We’ll likely replace the `Final` checkbox (which people rarely find without our help anyway) with groups soon: This is great, been waiting for groups for a long time! > [@mdubakov](#): > > Now threads will be collapsed by default and take less screen space. We got used to comments running in a long thread down the page, so having to open up to see replies is an extra step that takes away from the ability to just scroll and glance at the entire conversation in an entity. Would you guys consider allowing a setting so they don’t collapse by default? I would actually prefer they not collapse at all, and at least this way I could set up that I don’t have to click to see the response first… > [@mdubakov](#): > > and abandon features like comments resolutions and unread comments so far) I hope this doesn’t mean permanent abandonment! I waited about 2 1/2 years for you guys to return replies from the original iteration of comments that had threads, happy to wait still on resolutions to comments, but I hope you don’t give up on that! It would be a true innovation and allow yet another level of sophistication in Fibery around communication and clarity of work. Marking a comment as “resolved” without a way to say what was resolved is something in other tools that always left me wanting to know what happened, and leaves a hole in a team’s documentation (since you can’t provide the explanation alongside the “resolved” check mark). Just citing one of the requests for this [(https://community.fibery.io/t/resolving-comments/2824)](https://community.fibery.io/t/next-iteration-of-comments-commenting-when-resolving-assigning-as-tasks-reminders/527) in case any new users would like to support this. And just have to point out for the record that you have been around such a feature before: > [@Next iteration of Comments - Commenting when Resolving & assigning as tasks/reminders](https://community.fibery.io/t/next-iteration-of-comments-commenting-when-resolving-assigning-as-tasks-reminders/527/3): > > TargetProcess in fact has a great feature where you can configure workflow transitions to require a comment, that would be terrific to see in Fibery! Thanks guys and keep up the good work! --- _[View the full topic](https://community.fibery.io/t/nov-2-2023-collapse-replies-in-entity-comments-fibery-user-guide-chatbot/5364)._