September 10, 2026 / Hide parents without children in filters, Color coding for cards and text styles on Whiteboard

Small release today with some improvements and many fixed bugs.

Filters: Hide parents without children (experimental)

It sounds scary, but it is just a setting for hierarchical Tables and Lists that can solve one very specific problem. Imagine you have some hierarchy like Area → Feature → Bug and you created a filter that shows only Bugs that are In Progress. Without this setting you will see all features and all areas still, but maybe you want to focus only on those features and areas that have visible bugs? In this case just enable Hide parents without children in Filters menu and enjoy less entities.

Color coding for cards on Whiteboard

Color coding now works on whiteboard cards, just like in other views. Select a card, choose Color, and set up your color rules. If a card matches more than one color, the first one fills the card and the others appear as stripes on the left.

Text styles on Whiteboard

You can now quickly change text size using the new Text styles menu in the toolbar:

  • Normal text ⌘⌥0
  • Heading 1–4 ⌘⌥1 … ⌘⌥4
  • Custom size: enter any size from 4 to 999

Text styles work everywhere on your whiteboard: with regular text, shapes, sticky notes, and connection labels. You can still resize text manually or enter your own size. In that case, the menu will simply show the current size.

:butterfly: Improvements

  • Undo: Now you will not see batch undo/restore modal when only one item is selected
  • Automations: Now we have a new stylized avatar instead of an out-of-place :robot: emoji
  • Credits: Monthly limits get reset when you purchase a subscription
  • Performance: Client side performance improved a bit and CPU should be consumed less and you will have slightly faster load times and faster updates

:shrimp: Fixed Bugs

  • Whiteboard:
    • Wrong counter in button title when ‘Name is empty’ filter is used
    • Database gets unselected if you click on database name when closing filter popup by unfocused
    • Cards added over the frame, but not inside it if add it via multi-entity insert
    • No error on UI when convert object on whiteboard to the group entity if the limit is reached
    • Can’t use Left-Align and Top-Align for text simultaneously unless I select them in a specific order? And the indicator for which alignment mode is selected can also be broken fairly easily.
    • It’s impossible to quit text edit mode by Esc
    • In read-only mode, pop-ups for links in the text are not shown
    • View is expected to be created on click, not right after selecting ‘create a view’ option
    • Sometimes embed views are created too narrow
    • Hidden view should stay on the same layer
    • Broken arrow on moving of related objects
    • Whiteboard gets unusable if there are many sticky notes with author avatar
    • Min width and height are missed for widgets on Whiteboard
    • It’s impossible to increate some ArchiMate shape size after decreasing it to min size
    • Unable to type ``` (three back ticks) in a shape
  • Rich Text:
    • Tab key indents the bullet list instead of navigating table cells when a table is nested inside a bullet point
    • Old titles are shown for mentioned views and docs after rename
    • View Block: Entity-level views from another DBs aren’t shown in Recent Items
  • Permissions:
    • Admin can’t grant access to integration DB even if he has Architect + access on the Space level
    • Viewers can’t add inline comments to rich-text on Feed view
  • Fields:
    • Rename fields: Hyphen in field name is converted to space on save when name begins with a date
    • ‘Arrow’ button appears for any unit on selection- even for ones which have no visualization switcher
  • Export: Emoji ID instead of alias is shown in exported to markdown document
  • Filters: Do not show pinned filter icon if it is a filter group with empty filters only
  • Search & Recent Items: User role doesn’t look good in search
  • Custom Apps: Open in new tab link should be visible in usual mode
  • Integration:
    • HubSpot: Ticket misses contact, company relations
    • Google Calendar Integration: google calendar connector unable to fetch events when from date is missing
    • During integration resolve full address location instead of just showing coords
  • History: Event about revoked author (Created By) access is missing from history
  • Mobile: Bottom navigation disappears when the Android app starts
  • Notifications: Missing notification about assignment when user gets access to the entity via People field
  • Undo: Not informative error in Undo details if try to delete User/Avatar field via Undo
  • Desktop: Windows desktop app: stray vertical scrollbar in the top-right corner
  • Relation Views: Relation Table Show more drops context filter

P.S. Hugs for all of you just in case!

14 Likes

Thank you so much! These are very useful updates for the whiteboard. :star_struck:
I have a question: is it possible to set up color rules for entire board for all cards so that when a card is added - the color is applied automatically?
That way, whenever a task card is added, its status is immediately visible, and the color updates automatically if the status changes.:thinking:
That way, you won’t need to color new cards every time when you add the existed task.
Thanks again— we really appreciate it. :upside_down_face:

1 Like

Very cool!

Quick question: does it cascade up or down? As in, if an entity if both a parent AND a child, and it has no children, does it get shown? Or is it hidden, which causes it’s parent to then also be hidden. Is “child” only the most bottom level?

Cool, the video makes it seem like it is dont to one entity at a time, but I see its set for all entities on that database on that whiteboard. Just like it works on other views. Nice! @ID.000 this answers your question above.
This is pushing whiteboard closer to a data view. Which is cool, but I still stand by my view here: Split whiteboard view to a "Canvas" field, and a "Network" view

Its a bit hard to differentiate the Fibery logo and the new Robot guy, when looking through changes, I usually dont really pay attention to the Fibery logo since it’s less of something I control.

Lovely stuff this week. Thank you! :people_hugging:

2 Likes

Yes, works as expected!!! :star_struck:
[with colors for all new added cards]

:heart_eyes: Thank you, Fibery team!

3 Likes

Quick question: does it cascade up or down? As in, if an entity if both a parent AND a child, and it has no children, does it get shown? Or is it hidden, which causes it’s parent to then also be hidden. Is “child” only the most bottom level?

It cascades up from the most bottom child, e.g. in Product Area → Epic → Feature → Bug only those PAs would be shown that have Epics which have Features which have Bugs.

We are open to feedback and were thinking about making this setting more granular (i.e. specify what level to hide) but want to understand use cases better first

1 Like

:hugs: Hugs for y’all as well!

2 Likes

Integration:

  • HubSpot: Ticket misses contact, company relations :heart_eyes:
1 Like

Okay makes sense.

I’ve had ideas of calling it different: “Show all entities” vs “Show related entities”

Then per database the user can configure which is “Show all” and which level is “Show related”

So with your example, it would be something like this: Product Area (show related) → Epic (show related) → Feature (show related) → Bug (show all)

I actually started working on this in a Custom App (it also incorporates vertical vs horizontal layout). Had this idea for a view builder like this for a while, so its cool to see its almost, kind of, but not really yet buildable in Fibery!!

It does raise a question about: if “Show all” is on the bugs, and you filter out a product area, should it also filter out the Epics, Features, and Bugs? In my example I would say no, but in Fibery the answer is yes (and I think thats the right answer, but not sure)

Curious to hear what you think of this if you have the time to share.

Yeah, initial design had this ability to choose how far do you want to cascade. However, it complicated UI quite a bit especially for deep hierarchies. So, after reading all the feedback and use cases it seemed to us that it’s enough to have just one setting for the whole hierarchy.

1 Like