# Opportunities for "polish" **URL:** \ **Category:** Bugs & Issues\ **Created:** [September 26, 2022, 10:25pm UTC](https://community.fibery.io/t/opportunities-for-polish/3338 "2022-09-26T22:25:02Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [September 26, 2022, 10:25pm UTC](https://community.fibery.io/t/opportunities-for-polish/3338/1 "2022-09-26T22:25:02Z")
Not sure if this is a good idea, but I thought I’d start a list of what I consider minor bugs, issues, and perhaps even _small_ missing features that I see as very clear opportunities to improve the “polish” of Fibery and make it feel a lot more pleasant (lower friction) to use for everyday work. Starting out this will be an unordered, uncategorized list. I may break it out further into categories in some way if it grows large enough. And I hope to update this ongoingly (and will try to cross out/remove anything that gets addressed). Note that this list intentionally does _not_ include some larger things that have been called “polish” recently, such as the [Lack of Work Management features in Fibery (Reminders, Dependencies, Notifications, My Work, etc.)](https://community.fibery.io/t/lack-of-work-management-features-in-fibery-reminders-dependencies-notifications-my-work-etc/3319). Whether those are easy to address or not, I consider them more to be “features” and deserve or require their own, dedicated discussion. If I can encapsulate my intention here I think it would be that the majority of items listed here should not require much additional context or discussion to understand and address the problem (whereas improving e.g. notifications _would_). - [Clunky creation process for entities with formula-based names](https://community.fibery.io/t/formula-in-name-column-breaks-entity-view-of-relation/2751) - Enter key not supported to confirm date/time selection - Tab order on Entities is outright bad/broken ([still](https://community.fibery.io/t/improvement-to-tab-order-keyboard-field-navigation/966)) - [✅](https://community.fibery.io/t/changelog-october-7-2022-multiple-relation-views-experimental-quarters-in-timeline/3380) [Inconsistent and sometimes inaccurate title bar text due (I think) to Panels navigation](https://community.fibery.io/t/incorrect-browser-window-title-due-i-think-to-panels-navigation/3361) - ~~Sometimes the browser Title Bar shows the Entity name, sometimes the Database name, and sometimes the _wrong_ entity name (e.g. when that entity is collapsed, but title bar still reflects that and not maximized doc, even on browser refresh)~~ - Forced refresh with some panel navigation make things feel “jittery” and “fragile”/buggy - Necessity to Refresh some Views to get updated contents, e.g. with entity created via Automation (“no refresh” would be the ideal target) - Clicking on current location in Sidebar does not reload/refresh, thus I have to click to a different View, then click back, or press Refresh in browser - Inconsistent and often inaccurate display of current “location” in Sidebar - [“Recent entity” list for linking on Entity Relations Lists shows outdated names for entities](https://community.fibery.io/t/tofix-recent-items-entities-have-old-name-in-search/1176), both in the pick list _and_ after selection. If you open the linked entity, the name is different! (name of the actual entity is correct, name in the recents list is the pre-formula result) Also it seems fair to note that a number of these kinds of things _do_ get fixed with most of the regular releases. These are ones that stick out to me based on how much they impact my workflow, and how long I think they have remained unresolved. `Updated 10/11/2022` ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [September 28, 2022, 8:11am UTC](https://community.fibery.io/t/opportunities-for-polish/3338/2 "2022-09-28T08:11:55Z")
Thanks! Most of these things have been in our backlog, I’ve linked your feedback, and, thus, increased the chances of polishing happening. P.S. Sometimes I feel like you apply for our [Product Manager](https://fibery.io/blog/careers-product-manager) job in this convoluted way 😅. ---
**Author:** ![webinit](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/webinit/32/5548_2.png) [@webinit](https://community.fibery.io/u/webinit)\ **Post date:** [September 28, 2022, 11:38am UTC](https://community.fibery.io/t/opportunities-for-polish/3338/3 "2022-09-28T11:38:22Z")
Agreed! @Oshyan would be perfect for the role. ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [September 29, 2022, 2:17am UTC](https://community.fibery.io/t/opportunities-for-polish/3338/4 "2022-09-29T02:17:39Z")
Great, thanks! Do you have any advice/requests for how to handle additions I might want to make to the list above? I am not sure if Discourse will notify you if I edit the first post. I can be sure to post a Reply below and/or @ you. Or if you prefer I can just make a new topic, although ideally from my perspective I want to avoid cluttering up the forums with such “meta” things. Let me know what you prefer. > [@antoniokov](#): > > P.S. Sometimes I feel like you apply for our [Product Manager](https://fibery.io/blog/careers-product-manager) job in this convoluted way 😅. Oh yes, I am very convoluted. 😆 I would love to be able to actually work _on_ Fibery. Unfortunately since I live in one of the most expensive places in the US, the salary sadly cannot support me here. And I’m afraid I cannot move for Fibery - I love your software, but I love the California Bay Area more. 😉 ---
**Author:** ![webinit](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/webinit/32/5548_2.png) [@webinit](https://community.fibery.io/u/webinit)\ **Post date:** [September 29, 2022, 6:04am UTC](https://community.fibery.io/t/opportunities-for-polish/3338/5 "2022-09-29T06:04:43Z")
I suspected that might be the case. 🙂 ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [October 1, 2022, 9:32am UTC](https://community.fibery.io/t/opportunities-for-polish/3338/6 "2022-10-01T09:32:35Z")
> [@Oshyan](#): > > Let me know what you prefer. I personally prefer “one topic = one problem” approach. This way it’s easier for other community members to contribute their use cases and for us to prioritize and share specific updates. > [@Oshyan](#): > > I love your software, but I love the California Bay Area more Ha-ha, I can certainly understand that 🌞 ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [October 1, 2022, 4:12pm UTC](https://community.fibery.io/t/opportunities-for-polish/3338/7 "2022-10-01T16:12:47Z")
> [@antoniokov](#): > > I personally prefer “one topic = one problem” approach. This way it’s easier for other community members to contribute their use cases and for us to prioritize and share specific updates. Sure. My intent here was more to collect things that I think together collectively create a general “unpolished” feeling or which make working in Fibery not feel as good as it could. Obviously there are many such things, but these are my personal view of the most frequently-encountered ones. Other people’s view would no doubt differ. Maybe this is not a useful approach at all, but I thought I’d try it. 😄 ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [October 11, 2022, 2:44pm UTC](https://community.fibery.io/t/opportunities-for-polish/3338/8 "2022-10-11T14:44:30Z")
I have updated the first post. Sorry 😄 I’ll try to break these out into their own Topics as time allows. ---
**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:** [April 17, 2025, 1:11pm UTC](https://community.fibery.io/t/opportunities-for-polish/3338/9 "2025-04-17T13:11:17Z")
> [@Oshyan](#): > > Clunky creation process for entities with formula-based names Fixed > [@April 17, 2025 / leaf\_fluttering\_in\_wind Duplicate Field, Improve Entity creation flow when entity name is generated via a formula, Multi-accounts in Google calendar](https://community.fibery.io/t/april-17-2025-duplicate-field-improve-entity-creation-flow-when-entity-name-is-generated-via-a-formula-multi-accounts-in-google-calendar/8625): > > This release has several quality of life improvements for creators and users. Enjoy! leaf_fluttering_in_wind Duplicate Field Imagine you setup a long and beautiful single-select field for Tasks database and suddenly realise that you need it in Bugs database as well. You had to re-create it from scratch… No more! Now you can quickly duplicate basic fields (including single- and multi-selects) into another database. squid Improve Entity creation flow when entity name is generated via a…