Last release in June brings you My Work widget and some improvements in Desktop apps and Whiteboard View. We also fixed a lot of Gantt View bugs (but not all ).
My Work Widget on Home Page
Now you can see all work assigned to you on Home Page in My Work widget. It automatically discovers and displays all entities across your workspace where youâre involved â whether youâre assigned, own, or are mentioned in any People field.
My Work has three tabs: Started, Not Started and Finished. You can customize visible databases and fields, add filters, color coding and find entities fast.
Next step for Home Page is to let you embed views as widgets.
Desktop: Icons and Panels support for tabs
Tabs now display Entity or View icons to help you navigate faster and more intuitively.
Plus, when you have multiple panels open, tabs will automatically split to show them side by side â making it easier to work with several things at once.
Whiteboard: Link Sections to each other
You can now link entire sections to each other â not just individual objects within them.
I would urge you to back to the drawing board with this one. The whole point of fibery is that its un-opinionated. This is slowly introducing opinion. I personally prefer using a checkbox as âdoneâ rather than the workflow. And when things get complex, I use a different database called status. I never use workflow. I donât like it. Now this whole widget on my home by default for me and all other users on my workspace is useless. I feel this is backwards and goes against the fibery way of doing things. Its a big deal in notion because they canât have views across different databases. In fibery you can. Why not let the admins set up what DBâs to show? I really donât understand.
This is awesome!
Iâm not sure what changed, but it still feels a bit finicky, not snappy, and unclear which one is open.
I really like the new Open Item icon in the table view! Wasnât mentioned here, but really clean.
It is impossible to implement it without hardcoding. In next releases we will add an option to create any View on home page, here you will be able to do whatever you want with views.
In your case it will not work. Overall, it is hard to make a solution that will fit all cases. We tried to close majority problems, we will see how people will use it and what feedback we will have.
Allowing admin to setup views will not solve the problem as well, since admin will have to add/remove databases with domain evolution and this is quite fragile.
Is there something that designates ownership other than the Created By field? Most of the DBs that I have with a workflow field do not have a user field other than Created By and I donât have any entities in My Work currently.
Exactly! Thats the whole point of fibery though. Youâre not trying to build a tool that fits all cases. Youâre building a tool that lets people fit it to their use case.
This is interesting. I think it would make sense for the fields to be the same across all the tabs. Right now I added a DB name, and it was only visible for the active tab but not the others.
The icons will definitelly help. The panels as a secondary tab is an interesrting idea. Iâll have to see how it feels in practice.
What would make this even better would be if when managing databases, the favicon was of the current DB. Right now it shows the space icon and title. That means if I have 3 different tabs, showing 3 different databases in the same space, they will be indistinguishable for each other (they will all have the same icon and tab title).
OTOH I use it all the time because it lets me easily make custom statuses but also leverage the default coding for the three major âstatus typesâ (todo, in progress, done). I originally built in notion, which has a very similar concept, so I trained myself to leverage it a lot. The only thing I miss is that itâs harder in Fibery to show views by status group (e.g., group by status type) than it was in Notion.
We do use workflows, built for serious scaling in the future, but not the built-in workflow field.
Using a dedicated Database for workflows (instead of the built-in Workflow field) can be more flexible and versatile in the following cases:
When you need multiple workflow-like fields in the same Database (since only one Workflow field is allowed per Database).
When you want to store additional data for each state (e.g., description, responsible person, deadlines).
When you need complex relations between states and other entities (e.g., permissions, automation triggers).
When you want to reuse the same set of states across different Databases.
The built-in Workflow field is limited to a single, non-empty field with predefined state types (Not started, Started, Finished) and is best for simple progress tracking.
For more complex processes, a dedicated Database linked via Relations provides greater customization and scalability.
â
But, I see the intention of widgets in Home that show workspace-wide content:
So instead of hardcoded workflows with state types in Home, I suggest that everything in fibery, including Home widgets, is template-based meaning for example State Types can be a template and database that can be enabled and any workflow database can relate to that, such that they become accessible workspace-wide though the same parent State Types.
â
So I imagine a Home with widgets that by enabling them, create an instance of a widget template, such that they can be still configurable and can even be âresetâ to the original template configuration upon the click of a button. Nothing needs to be hardcoded.
Yes I know, by control-clicking the state in the worflow field (a hidden feature) but workflow states are not databases, so they will now show up in views, no relations or lookups possible, you cannot filter states, and I wonder in what use case the custom workflow fields would be helpful?
Can you give an example?
Still, I donât see enough value at the moment in workflow fields other than a quick solution for a workflow that does not need flexibility and is indeed opinionated.
In my opinion, the workflow field should be refactored for the States to be just normal databases, similar to what we want with the current Comments system.
The only benefit I see in the workflow field is the built-in sequential relation, but that again forces to use the three State Types. So ideally fibery should allow for automation templates such that automations are more accessible fore non-technical users. But this topics has already been suggested a number of times (workflows UI instead of the current automations UI)
Would me nice to be able to have at least two columns and more widgets. Maybe text widget for home.
Regarding embedding views I think the better option is to create view inside home. This gives us similiar option as my work but without restrictions where workflow and people field is enforced. And doesnât mess with navigation panel. I think it should be excluded from panel. But overall idea is good.
Really appreciate the small details like the arrow button on a row now being with a border, and only appearing on mouse-hover. It makes it much more clear where to click. Itâs those things that really make it more enjoyable to use the product.
While the current âMy Workâ widget is largely useless for us for the same reasons others have said, looking forward to adding other widgets to âHomeâ soon.
I assume weâll be able to hide the current âMy Workâ widget and replace it with whatever custom view we want that actually shows work in the way we want? Really hope weâre not forced to have widgets on the homepage that we donât want to use.
In the future, will we be able to add 2 or more widgets to the same row, just like every pretty much every other âdashboardâ in the world? I hope so, and then I hope that functionality could come to entity views too!
Regarding the âmy workâ homepage, I like the idea. But ideally we customize this, so that the company determines what all users see here. So either:
The admin can choose an existing view that is shown here
The admin can change the filters / sorting etc of the âmy workâ widget
We already have a view that shows a relative (user = me) âmaster task listâ for everyone in the company:
But now we have to ask each new user to make this view a favorite, and encourge them to check it regularly (which takes a few clicks to get there). If itâs the first thing that they see on the home page (with just one click), then it almost canât be missed. Itâs lowers the bar immensely.
For one, I donât think users should be able to edit what appears. They can turn on whatever fields they want, apply whatever colors they want, and turn on/off entire databases.
This seems like Admin privileges that slipped through the cracks.
Additionally, if the workflow field is being used to toggle a status rather than managing a linear progress, it will be showing entities that have long been dealt with.
Not a fan of it being rolled out and visible by default.
).
Improvements
Fixed Bugs
