Hello,
Will it be possible to introduce a Personal section on views Sort the same way you did on filters ?
On a project for example, not everyone wants their stuff sorted on the same way. Some will base de sorting on starting date of the project, other ones would like to move manually the things, etc…
this is in plans for July/Aug
Thanks for the feedback.
Another friction point I see : if I have a project that contains a list of tasks, and that tasks list can be viewed with different views, if I apply a Sort on one of them, the other views are affected.
Let say that I want a List view with a sort and a Gantt view without sort, I cannot move manually my tasks on my Gantt because there’s a sort on my List view.
Hello 
Would it also be possible to support temporary ad-hoc sorting? 
For example, a user clicks a column header and temporarily sorts the records by that field. This should not change the global View sorting or the user’s saved personal sorting.
After refreshing the page, the View could return to its saved global sorting or the user’s personal sorting, if one is set.
This would be very useful for quickly checking or comparing data without affecting the default setup for everyone else.
Did you imagine that these ‘personal’ sorts would apply secondarily to the ‘global’ sorts? Or would they override?
Since you compared to personal filters, it’s worth commenting that these are applied in addition to global filters.
For sorting, I have a gut feeling that this is not very useful (i.e. if the global sort is by Name, adding a personal sort by Creation Date will have no effect, except where multiple items have the same Name)
Good point, for Sort option, personal settings should override the global one but only for the User obviously.
On my point of view, as Fibery is a nerd tool, on every option you build we should be able to force a setting (when relevant), set it as an option (when relevant) or set a default value. When architects build processes, they need to think about “what my end users should see when they open this and what should they be able to do ?”.
On the example of Filters : I want to force filter A and filter B as a default for everyone. And additionally, everyone can add other filters. (Why not adding a switch to say “force global settings for everyone” on Filters and other components)
On Sorting : I want to set a default sorting (the most used one for example) but not everyone works the same manner so the end user should be able to override it.
This can apply to personal Users preferences too. If it was possible, I would enable Email notification by default for every new user. Because for a non nerd guy, it’s pain to configure everything.
Isn’t this exactly what is possible with Global/Personal filters, which can optionally be pinned as Quick filters?
(or were you describing current behaviour rather than making a request?)
For Filters, yes it is. I was enumerating some examples (already implemented or not) in order to share the global vision of the idea.
EDIT: Sorry, I was thinking about another idea behind this. When I said :
I was thinking about the idea of “forcing”, “set as optional” and “set as default”. For me, this 3 settings have the following behaviour :
We can apply the same idea on Sort (or on other components), taking into account that a Sort can be overridden by the personal settings.
I see this as a helpful paradigm. It highlights that there are different reasons or purposes for applying filters/sorting/whatever. For sorting, I agree that it’s nice if a user can adjust this for themselves. Many people are fairly aware of sorting from other programs, and some like to adjust the sorting frequently in order to get different views at the data or just as a method of searching for something specific. It becomes like sorting email where we have a default sort (newest at the top of search results), but the user can apply other sorts if they want to (by subject line, sender, oldest at top, etc.).
I think an important thing to consider would be if a user setting would be remembered. After a view is closed and later opened, does it open as the architect-defined default, or does it remember the user’s last setting? I imagine different users would have different expectations on this. Also, should there be the same behavior for relation views within an entity view?
Good point, I would say : if the User changes the default, then the User setting should remain. But he should have the option to come back to the default.
The idea is to apply this vision on every View. I think the object is the same.
I’d like to add one more related use case: temporary column sorting . (adding info for my thoughts above)
This is slightly different from saved personal sorting.
Example: we have a table with columns like:
Building name
Wood used
Glass used
Concrete used
The global/default sorting is by Building name.
But sometimes I just want to click the “Wood used” column header and temporarily sort the table by the highest or lowest wood usage. Then maybe click “Glass used” or “Concrete used” to quickly compare values.
In this case, I don’t want to change the global sorting, and I don’t necessarily want to save this as my personal sorting either. I just want a temporary sorting state that overrides all other sorting only for the current session/page view.
After refreshing the page or reopening the view, it should return to the saved global sorting or saved personal sorting.
So maybe there could be additional level:
Global/default sorting set by the Architect.
Temporary column sorting by clicking a column header, which overrides everything only until refresh/reopen.
This would be very useful for quick checks, comparisons, and data exploration without affecting the default view setup.
