Add emoji icons for Entities of tag-like Databases like Category, Status, or Team to make your workspace shine:
Many of you (and us!) have already put emojis in names. Now we’ve made sure the icons look alright throughout Fibery: in relations, search, history, etc.
Icons are especially useful when you use regular Databases in place of Select Fields (e.g. to share Status between Stories and Bugs) or Documents (e.g. to store extra info like Maintainer).
Add Icon Field to a Database to pick icons for its Entities
Search comments
From now on, we index comments in addition to rich-text Fields. An icon indicates that the match occurred in a comment.
One less reason to go to Slack to discuss projects and tasks already present in Fibery, ∞−1 reasons left.
Markdown import now supports both Notion’s and Fibery’s export format. It automatically creates the document structure during import and removes the ids from files and folder names.
Fixed Bugs
We’ve put some love into Space and DB renames:
Space rename throws error if there are context views in left menu
Oops error on views (table, timeline, board, calendar, feed, list) in case of renaming Database which is used as source in separate tab
Oops in left menu if rename both types which are used in Smart Folder
Oops, error in left menu on twice renaming space if it contains Smart Folder
Renaming a DB throws an exception for opened context view
JS in console while rename app with enabled workflow extension
Values in ‘State’ column hang on 2nd changing database name
Failed to load view error on the red band if open view while DB rename is in progress
Other areas have gotten some polish as well:
Import / Export inconsistency
Auto-focus search bar in emoji picker on open
Issue with default picture for ‘No image’
Created in context grid entity does not get linked to parent
z-index issue for emoji when single/multi select field is created in table column
Website: existing auth/password sessions should reset when resetting password
Vertical scroll stops working for embedded views
Make Plan and Billing page available for admins only
To avoid polluting my workspace or having to deal with a test workspace (i.e. laziness), can you clarify whether the Notion import also correctly handles database entries with Markdown page contents? Notion has both hierarchical pages (which I assume is what is new and correctly handled in this update) and page contents of databases. The latter was not supported in Fibery, and I’m hoping it too now works with this update. If not, then soon?
In this release, we focused on improving markdown import, including better support of the Notion markdown export. We specifically worked on the hierarchical structure and removed the notion_id during the import. Since the page content of the database entry is part of the Notion export as a markdown file, the import works smoothly. However, it does not mean that the Notion export will build up the database and the documents. This will be a separate feature, but unfortunately, we don’t have an ETA for that yet.
Next, we’ll tackle the CSV import to merge v1 and v2.
Nice update! I would love the ability to set an icon from a formula. Any chance there are plans for this?
For example, being able to automatically change your task’s icon based on the state would be a huge aid in visualizing what is attached.
And like @Matt_Blais said above, being able to do the same for the background color of your relation links. Allowing both icons/link color to be formula driven would help make Fibery a lot more intuitive
And you are right, very much a step towards eliminating the need for Slack when you communicate in Fibery. My team already did this and now we can actually find stuff we wrote in comments, great stuff! Wasn’t even holding out hope for getting this anytime soon, thanks so much for prioritizing this!
I really love the option to add emoji icons for entities. What would make it even better if we could set a default icon for new entities in a database.
Certain entities in our workspace are given fixed icons to create a visual distinction between different types of data. For example: Template entities gets this icon
As new entities are gradually added (both by us and by the user) it is nice when we don’t have to set which icon we want per entity, but that at database level a certain default can be set when a new entity is created.
Is this something you think would be possible in the near future?
Yep, should be fine by now. Please ping us via Intercom if comments are still not being indexed.
Note that inline rich-text comments are not indexed yet, only the ones added via the Comments extension.
Great to see the new feature allowing emojis for individual entities! However, I think we can go further:
Default Emoji for Databases: With more than a few databases, color-coding becomes less effective. A default emoji for each database would be more distinguishable and efficient.
Formula-Based Icons: As @Matt_Blais suggested, let’s take it up a notch by allowing a formula to determine the icon. This adds dynamic customization.
Inclusivity: This is also a win for colorblind users, making Fibery more accessible.
Current Database Color icon setting:
Current Entity emoji/Icon setting:
Example mockup for the Database emoji/icon setting:
@antoniokov Is it possible for icons to be inherited from a relation?
I was able to create a lookup field that looks up the icon from a relation. However, it doesn’t seem to affect the entity icon itself. This would be quite a helpful tweak by allowing users to define the icons by types and have them propagate through.
Pick a custom icon for any Entity
Search comments
Import markdown from Notion/Fibery
Fixed Bugs
Any chance there are plans for this?
