# Oct 26, 2023 / šŸ’¬ Replies in entity comments, Specify numeric values for select options **URL:** \ **Category:** Changelog\ **Created:** [October 26, 2023, 1:44pm UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334 "2023-10-26T13:44:57Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 26, 2023, 1:44pm UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/1 "2023-10-26T13:44:57Z")
## šŸ’¬ Replies in entity comments Last week we experimented with comments in a separate panel, but feedback was negative (thank you!), so we iterated again. We removed panels for comments and just added replies to main entity view. To add the first reply, find `Reply to Comment` icon in a comment and click it. ![Screenshot 2023-10-26 at 10.53.37 AM (1)](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/0e1ffac8c2d5ee7daa46672294a24f190c92ad57.png) Weā€™ve added a comments icon in the top right entity menu. When you click on it, it scrolls you to the first comment. NOTES: - Replies work in entity-level comments only (not in rich text and documents comments). - Now we are working on comments resolutions, it will be possible to collapse resolved comments in future releases. ## šŸ’… Specify numeric values for select options Now you can add numeric values to single- and multi-select fields. Find Advanced section and enable `Specify numeric values for each option` switcher. You will see fields where you can put values. You can use these values in formulas. For example, if you have a single select field named `Ease`, you can access a value this way `Ease.Value`. ![Screenshot 2023-10-26 at 4.27.19 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/5096a0349aecc3b41ff421aa194b951132c0bb56.png) ## šŸ§¹ Get rid of ā€œUntitledā€ when user has no access to Entity When user had no access to some databases, we showed cards as `Untitled`. They confused users and added visual clutter. Now we hide entities user has no access to from Views and dropdowns. In many places itā€™s useful to indicate whether a relation Field is empty or not, so we display `šŸ”’ Private Task` instead of the current `Untitled`. ![Screenshot 2023-10-26 at 4.31.43 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/6940857de5df0dee984ed48072c48f8335f850ce.png) ## šŸ§© Grid View improvements and bug fixes - Data editing is polished - Add new rows is polished - Rows drag and drop should work nice now - Save columns width for duplicated grid - Missing uploaded avatar in context grid - JS error in console if grid is scrolled during drag&drop columns - Collapse/expand arrows donā€™t appear for first level of hierarchy in some case ## šŸ¦‹ Improvements - Toasts design is improved. Now toasts looks better and positioned on the bottom of the screen. - Some style improvements here and there. - Delivered to (BCC) email is synced into `Delivered To` field. It can be used for gmail aliases to retrieve exact alias used as email. For example if email [fibery.dev+test@gmail.com](https://mailto:fibery.dev+test@gmail.com) is used as BCC then it is synced to `Delivered To` as text. ## šŸ¦ Fixed Bugs - Pinned columns get reordered when hide not pinned column in some case - UI issues with calendar control - New comments are not loaded for shared entity - Error message in automations when user deletes formula in Notify action and saves rule - Button menu is partly hidden under right panel - Duplicate key issue for automations ## šŸ¤« P.S. Entity-level permissions are ready (with some scope) and weā€™re testing them with selected group of customers. Anton asked me to keep it secret, but I just canā€™t resist. Sorry, Anton, you may revenge me in the next release. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 26, 2023, 1:45pm UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/2 "2023-10-26T13:45:43Z")
---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [October 26, 2023, 2:47pm UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/3 "2023-10-26T14:47:23Z")
> [@mdubakov](#): > > Replies work in entity-level comments only **(not in rich text and documents comments).** I sincerely hope that Rich Text comments will eventually have the same capabilities as entity-level commentsā€¦ šŸ˜ø ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [October 26, 2023, 2:50pm UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/4 "2023-10-26T14:50:38Z")
Awesome release šŸ¤© Comments look great! > [@mdubakov](#): > > P.S. Entity-level permissions are ready (with some scope) and weā€™re testing them with selected group of customers. šŸ„³šŸ„³šŸ„³šŸ„³ ---
**Author:** ![Nevil\_Hulspas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nevil_hulspas/32/4703_2.png) [@Nevil\_Hulspas](https://community.fibery.io/u/Nevil_Hulspas)\ **Post date:** [October 26, 2023, 5:25pm UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/5 "2023-10-26T17:25:30Z")
Great release! Just a bit bummed about the fact that replies to comments are not collapsable. Nesting replies does make it somewhat better, but the fact that you still have to scroll endlessly in long threads doesnā€™t improve workflow. I know this functionality wasnā€™t here before, but commenting was the number 1 complaint from our team about Fibery. Now I understood that this is coming in the release of resolving comments, so curious know the timeline on this @mdubakov Really hoping for this very soon: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/02cef22536e4f0ee5aeca5a9b4081adfcb9544b6.png) ---
**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\ **Post date:** [October 26, 2023, 7:17pm UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/6 "2023-10-26T19:17:04Z")
This is great news! šŸŽŠ Super happy with the nested comments. Canā€™t wait for folding and resolution still. šŸ™‚ Also excited to hear that the new permissions model is coming along! šŸ¤© Thanks for the hard work! ---
**Author:** ![Marloes](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/marloes/32/5926_2.png) [@Marloes](https://community.fibery.io/u/Marloes)\ **Post date:** [October 26, 2023, 8:19pm UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/7 "2023-10-26T20:19:04Z")
Wow, what an awesome release!! Thank you guys. P.s. Tested the new comments this afternoon. Love it! ---
**Author:** ![Sylvain\_Vuilliot](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sylvain_vuilliot/32/1771_2.png) [@Sylvain\_Vuilliot](https://community.fibery.io/u/Sylvain_Vuilliot)\ **Post date:** [October 27, 2023, 11:37am UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/8 "2023-10-27T11:37:18Z")
> [@mdubakov](#): > > ## Grid View improvements and bug fixes > > - Data editing is polished The new grid is very powerful and I use it a lot to replace table and list views. I donā€™t know exactly which improvement was done to editing but the long standing bug about loosing the first letter/number when you start editing a cell is very annoying. Iā€™m surprised to be the only one to complain. Do I need to fill a bug report or something ? Thank you all ---
**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:** [October 27, 2023, 11:41am UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/9 "2023-10-27T11:41:24Z")
Can you post an example (video) showing this behaviour. Iā€™m not aware of this bug. ---
**Author:** ![Robert\_B](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/robert_b/32/7198_2.png) [@Robert\_B](https://community.fibery.io/u/Robert_B)\ **Post date:** [October 27, 2023, 12:30pm UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/10 "2023-10-27T12:30:59Z")
Awesome update! Numbered dropdowns and more changes to grids. What a day to be alive. ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [October 27, 2023, 8:00pm UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/11 "2023-10-27T20:00:05Z")
> [@mdubakov](#): > > Now you can add numeric values to single- and multi-select fields. Find Advanced section and enable `Specify numeric values for each option` switcher. You will see fields where you can put values. You can use these values in formulas. For example, if you have a single select field named `Ease`, you can access a value this way `Ease.Value`. Is it possible to add this to Workflows so that we can easily determine the percent of completion? e.g. 10 issues within 1 epic, all `beta`, completion = 80% based on weight assignment. ---
**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:** [October 28, 2023, 7:17am UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/12 "2023-10-28T07:17:56Z")
You can already do it yourself (use alt-click to open a state, add a field, and then set the value for each state). But we will be making improvements to workflow soon as well. ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [October 28, 2023, 10:19am UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/13 "2023-10-28T10:19:51Z")
I tried this before and it didnā€™t appear to be working. Will test and reach out to support if necessary. Thanks ---
**Author:** ![Sylvain\_Vuilliot](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sylvain_vuilliot/32/1771_2.png) [@Sylvain\_Vuilliot](https://community.fibery.io/u/Sylvain_Vuilliot)\ **Post date:** [October 30, 2023, 1:34pm UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/14 "2023-10-30T13:34:21Z")
Here is my experience in the new grid: - in a text column, when you start to type, the letters are added to the current text (instead of replacing it) but no letter is lost. - in a number column, the first key is lost and the following ones are appended to the current value (instead of replacing it) - in other columns types (date, select, relation), the first key is lost, and the following ones are used to search in the picker. See the video where I type ā€œ123ā€ in every case (with up-to-date MS edge on windows, with not extension or other strange utility) ![Screen Recording - Made with FlexClip](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/8ca6c3aad82f82a327aa1145f0ce4c4b56a1401e.gif) ---
**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 7, 2023, 6:27am UTC](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334/15 "2023-11-07T06:27:46Z")
> [@mdubakov](#): > > Toasts design is improved. Now toasts looks better and positioned on the bottom of the screen. I still would love to see larger use of toasts, I noticed even Notion has some now in more prevalent cases like when creating somethingā€¦is there any chance you guys would start to add Toasts around Fibery? I canā€™t even really think of any time Iā€™ve seen a toast pop up lately in Fiberyā€¦ Here is my request about it: > [@Large-Scale use of ā€œfloating boxā€ pop up when activity in Fibery aka "Toasts"](https://community.fibery.io/t/large-scale-use-of-floating-box-pop-up-when-activity-in-fibery-aka-toasts/450): > > Hi again, I wanted to suggest that as you guys move forward, you do as much of an implementation as you can across Fibery of the ā€œfloating boxā€ pop up that would occur everytime an action is taking in Fibery. Iā€™m referring to something like the small modal that emerges in the current version of Gmail when you delete messages, send, etc. on the bottom right. A few apps, such as ClickUp and Jira, do this with just about every instance of an entity/task creation. Itā€™s a great feature as it allā€¦ Thanks!