I’m desperately looking for All-your-work-in-single-view.
The primary reason why we’re trying to move over from Clickup is because we just can’t find open work. It’s always hidden in some form somewhere in Clickup; either because we can’t do a global filter easily enough, or it sits in a doc as a comment. (Woe be onto you if you use global views in Clickup…)
I want to be able to setup a single view that goes through all entities and shows all open work, in any form. Just a single point that people go to that they know is up to date, always, with ANY open work that remains.
We’ve already moved to entities-as-documents in Fibery because of this.
However, comments are a thorn in our eye because you cannot:
Assign them to people
Filter in views on open comments in rich text fields.
Associate status or priority to them.
I’ve tried to work around this by hacking comments through entities or highlights - but both simply don’t have good UX for any of the main workflows. I’ve also tried using formula’s but haven’t been able to get anywhere. Comments live outside the Fibery ecosystem.
My ideal workflow being that I can construct a view that shows all entities with specific statuses (tasks, goals, epics, comments, docs) that are assigned to me.
To be honest you’re asking for a very unusual functionality. I’m not sure if I’ve seen any product/project management tool that allows to assign comments. Other than that everything else is doable in Fibery.
We’re aiming of having the same setup very soon and it should be a very straight forward affair.
Whats stopping you from making a view and adding all the DBs you want to show, and filter by “Assignee” = Is me? Genuinely curious to see if i’m missing something here.
Here’s the thing though, a well set up workspace should not have changes to the schema for a while, until the process changes and then the workspace needs to change. You are new encouraging people to create a new tasks db every time they have a new project, because now they don’t need to make a tasks view as its aggrigated in the “My Work”. But this isn’t how Fibery is meant to work.
Set up takes a long time, yes, but if done right, you shouldn’t be adding new db’s or new fields until the processes change. And when they do, yeah you’re gonna need to go adjust views, but thats part of it!
I have really hard time trying to stretch My Work widget to “You are new encouraging people to create a new tasks db every time they have a new project”
In next releases we will add an option for users to create Views here.
Then we will consider an idea to let Admin forcefully add Views on all users home pages.
Maybe its a bit of stretch indeed. I’m trying to say that it’s solving a problem that should not exist if using Fibery in the right way. A rule of thumb I follow and encourage others when building in fibery, is to try to build in a way where you don’t need to add more DBs / fields as you grow.
All of these:
Are not something you SHOULD be doing so frequently in fibery. If you are, you’re doing something wrong. I think. If you disagree, im happy to hear it!
I appreciate you engaging in this discussion, and I apologise for starting a bit hostile. I really do want success for fibery as a product and company, this move is just baffling to me.
We build My Work this way based on several assumptions
Fibery is flexible and initially workspace evolves a lot. It is quite hard to keep up with these changes and even if admin is willing to, it is not always easy to add databases to some relevant views
From the start many users don’t want to learn things, they just want to see assigned entities
Home Page is a place for widgets, if some user does not need some widget, it is easy to disable it, we might add more and more widgets and some of them will be unusable for you, that’s fine, and I don’t see how it can be bad
My Work definitely does not close ALL cases, but we hope it closes many. We will find out this very soon.
Additional power will come with custom view widget.
And then we will have to decide should we give admin any power to customize other users dashboard. So far it looks like we should do it based on initial feedback, but it is not decided yet.
From the start many users don’t want to learn things, they just want to see assigned entities
Absolutely – this is super useful. A ‘default’ widget that rolls up all the ‘assignments’ is extremely powerful in many cases. It’s easy to turn off if not needed. I’ve already turned it on and started using it.
One suggestion: it would be nice if I could create custom filters that turn on or off different databases. For example, maybe right now I only want to look at Projects I’m assigned to – it would be great if I could just click a button and switch to that filter set (like Custom Filters buttons in Views). Then I could click a different one and look at Bugs. etc. It would make the home page a natural default instead of getting drowned in everything assigned to me and just ignoring home page and going to a custom page (which is fine, but this would make the home page amazing).
Home Page is a place for widgets, if some user does not need some widget, it is easy to disable it, we might add more and more widgets and some of them will be unusable for you, that’s fine, and I don’t see how it can be bad
Not bad at all!
Additional power will come with custom view widget.
And then we will have to decide should we give admin any power to customize other users dashboard. So far it looks like we should do it based on initial feedback, but it is not decided yet.
I strongly vote for this – at least where the admin can provision a custom view as a ‘standardly available widget’ that users can turn on or off if they want. It would be a much more ‘new user friendly’ way than having to tell them to favorite a specific Document that I’ve created with custom views. It would provide a brilliantly simple onboarding experience for new users.
Makes sense! I think these problems are very much real, but I’m still not convinced that adding a home page with widgets is these solution.
I think embedding existing views as “widgets” could be nice, then changing the view in the view section will change it in the home, instead of adding yet another view that needs to be updated.
Its not bad if defaults are configurable by the admin. Or else it will be confusing that the first thing i see is 5 widgets that are not at all relevant to me.
But I feel like I might be in the minority with this looking at the rest of the reactions… Fibery is so so so powerful and I feel like 80% of people (including some of the people in the Fibery team) don’t know the power / don’t utilise it. The workflow field is less powerful than a database + relations.
But I feel like I might be in the minority with this looking at the rest of the reactions… Fibery is so so so powerful and I feel like 80% of people (including some of the people in the Fibery team) don’t know the power / don’t utilise it. The workflow field is less powerful than a database + relations.
Agreed - but it’s sort of like a jet engine vs a 2-cycle engine. If all I need is the 2-cycle engine, then it’s a lot easier to carry around … i.e., a lot less institutional knowledge to know how to maintain (it’s more intuitive for multiple people) and more ‘just works’. The database + relations should be available when I need a jet engine to solve specific use cases. Workflow is so common that it justifies a ‘pre-baked’ solution for most people. The beauty of Fibery is that when it doesn’t I’m not locked in.
I’m all for having simple tools that lay users can easily grasp and pickup quickly, and I think the My Work widget is addressing that. Also, it’s easy enough to disable the widget in the “Customize” menu.
It would be nice if admins could set a default layout for the Home page for all users, then users can adjust if they want. Or at least allow admins to create widgets that users can easily select from the “Customize” menu. I think it’s too much to ask lay users to essentially become “Creators” of their own Home pages. Our people barely use the Private space for this reason. Other than the native documents feature, the only views I’ve seen in people’s Private space is the ones I’ve helped them set up.
Great question! I tend to prefer things that don’t break users’ current workflows, but I see how this can quickly become complicated for a single page that both admins and users could edit, to some extent. One idea is for widgets to continue the same dual approach as filters where the admin sets the global filters and the user sets personal filters. I imagine this is baked in for the future “views in Home page” feature, and I noticed this is how the My Work widget is made (where Fibery set the global filters). That way if I make changes to already existing widgets, it is on the “admin stack” of the widget, but the “user stack” keeps the user’s personal settings.
If I’m changing the location of an old widget, I wouldn’t want this to make the change for currently existing users.
For the location of new widgets, I would expect it to appear for all users, similar to how Fibery activating the My Work widget made it appear. Again, I can see how this would become complicated if users are able to readjust the positions of widgets for themselves. This begs the question “where does the new widget appear”. Currently, it seems like widgets have fixed locations, in which case the answer for me is an easy “put the new widget below the other default widget I have set”. In other words, if I have widgets X, then Y, and I create widget A and put it between X and Y, then for users widget A should appear directly below widget X.
But if users can reposition widgets, then it may be better for the new widget to appear at the top, as in highlighting a new feature (they can then move it wherever they want). Ideally I would want it to have a similar behavior as I mentioned in my previous paragraph (where it appears below the same widget as set in the default layout), but I realize that we are looking at a huge number of possible configurations if users have a lot of freedom with the layout.
So, that’s all a thought exercise. I don’t fully know how your backend works, so some of what I mentioned might be untenable. But hopefully this is helpful.
