While we’re working on Fibery Mobile , new permissions core upgrade and re-writing our AI Agent almost from scratch , we still can deliver some useful things to our adored users.
Specify which Entity View to open based on some field value
You can now set rules that open a specific, pre-configured Entity View based on a field’s value — like Project Type, Feature State, Task relation, and more. It’s a simple way to show the most relevant information to users when they open an entity from any place.
It’s already working for ClickUp with Notion coming soon. You can also import/sync People in your own custom integration. We’ll update the docs soon — meanwhile, don’t hesitate to reach out for help.
Do you miss this in other integration? Please let us know by sharing your use case.
Improvements
Permissions: capabilities that Observers (aka read-only users) cannot receive are shown as such in access audit.
Activity log: inaccessible entities are displayed as Untitled instead of Private <Task>.
ClickUp integration: users are added to Fibery as Observers by default, although you can sync them as a separate Database or skip altogether.
Fixed Bugs
Whiteboard:
Black color instead of grey is shown in pen color palette in dark mode
Arrow is not drawn properly when images linked until user refreshes whiteboard
Error when click on actions button (…) on whiteboard in public Space
When selecting an arrow type in the menu all connectors switch to one type
The border is misplaced on changing size of text on line
JS error on removing section name
Audit History:
Integration Databases always miss createEntity capability in access audit
Inaccessible entities are displayed as Untitled instead of Private <Task>
Flexible Domain: It’s impossible to merge parent entities if relation field is marked as required from the child side
AI Agent (Build mode):
Format value is missed for created Number fields
Agent populates defaultValue in form with dynamic date which is not allowed
CSV import: CSV import issue if file has column named ‘id’ and contained duplicated data
P.S. Share your emotions or feedback, we always happy to hear from you.
Lovely stuff! Curious what’s to come from the new AI Agent.
Some thoughts as always :))
This is cool, but I was really hoping there would be user context here. If assignee = me, open one view, if its not me, open another. This was the main use case I saw. I also notice there’s no option for filtering on collections, ie: contains any of, contains none of. And there’s also no “is empty”, or “contains”. Ideally the filters here are the same as filters configurable in views (incl. filter groups). Not sure if this is on the roadmap for improvement now, some time in the future, or not at all.
But it looks a bit off when there is horizontal scroll in the main container. The nav feels like it should be behind the panels, yet it actually goes on top of the panels.
Even in things like table or board view , the nav feels like its going in front when scrolling horizontally, when in this new style it feels like its behind.
And the line above Help and Support and below Workspace/Personal goes all the way to the edge. Which maybe should stop a bit before the edge maybe? Not sure.
Completed agreed - love this feature!! This is one of this ‘gift’
surprises you didn’t know you wanted and are completely excited about
once you get it!
Interestingly, we had exactly 0 requests to add assigned = me, most use cases were around exact field value. We are not going to complicate things here so far, but we will collect feedback and decide if it will be necessary.
I second more contexts – I’ve wished before that I could set a view by
role (e.g., of the person opening it) – and maybe ESPECIALLY by where I
opened it from. For example, if I opened it from the project relation
field, then open it in X view, but if I open it through the budget
relation, then open it in Y view (but this sounds more like a link issue
then a rule). I wonder if you could specific in a View which entity view
to open? For example, in a “Budgets” view I could specific that the
entity opens in the “Money” tab, and in the “Projects” view I could
specific it opens in the “Project Status” tab? That would be absolutely
amazing, and enable very user-friendly UI. Of course, if it’s not
specified, then it would just default to the first tab or whatever.
Team or Job function is another use case that would be relevant to us
Like, if a “deliverable” was being viewed by someone on the “QA team”, they would have different buttons or fields shown than things than people on the “production team”.
Normally I’m a cheerleader for releases, so apologies in advance. I guess this change to Entity Views must be why I woke up this morning to have all my entity views now with collapsed Properties sidebar. And on my other (work) account they are even defaulted to 1-column mode. I think I recall in the past this was something to do with me not having changed the defaults and so the defaults got updated and overrode what I had or something. I wish that wouldn’t happen, but if it has to, well, still strong disagree with defaulting to 1 column and/or collapse properties sidebar state! Is there some way I can bulk fix this across all DBs? Yes it only has to be done once per-DB (I think/hope), but this is the 2nd time something like this has happened and it’s frustrating to have to go through again.
Also…
This strikes me as a bad way to handle this. “Untitled” is an actual state or even a name in some cases (like if a name defaults to “untitled”). Why not just say “inaccessible”, “no permissions”, “na”, or something else that’s actually accurate? The entity is not untitled in this case, is it? If it’s not literally untitled this is not the way to handle it IMHO.
Actually, we are fixing a bug where “inaccessible entities are displayed as Untitled instead of Private <Task>” but I can see how the announcement makes it read like the reverse.
Yay, thank you for the quick response! You guys are the best. I do see some of them fixed, though at least one DB was still in collapse state. Perhaps because I toggled it and it remembered my change, I don’t know. But hopefully all the others are back to the proper default, 2-pane, uncollapsed state.
This has always been my vote. I love this release but will only be able to use it in a couple spots. The majority of places I want this would only work in the opposite direction. Dictating entity view by the view you open it from. Basically when creating a view, selecting the entity view to open in the levels configuration. This would be a game changer for us
, new permissions core upgrade 
and re-writing our AI Agent almost from scratch 
, we still can deliver some useful things to our adored users.
Specify which Entity View to open based on some field value
This is a Pro plan feature
Improvements
Fixed Bugs
I guess this change to Entity Views must be why I woke up this morning to have all my entity views now with collapsed Properties sidebar. 
And on my other (work) account they are even defaulted to 1-column mode. I think I recall in the past this was something to do with me not having changed the defaults and so the defaults got updated and overrode what I had or something. I wish that wouldn’t happen, but if it has to, well, still strong disagree with defaulting to 1 column and/or collapse properties sidebar state! Is there some way I can bulk fix this across all DBs? Yes it only has to be done once per-DB (I think/hope), but this is the 2nd time something like this has happened and it’s frustrating to have to go through again.
