Question for Jobber Team: Why Are Filter and Sort Settings Not Persisted?
Across every core page, Jobber relies on sortable and filterable lists. Filter and sort settings are not persisted, not across sessions, not across navigation, and not even within the same page during a session.
This forces users to:
- Reapply filters
- Re-sort columns
- Rebuild the same view they just set up moments ago
Workflow comes to a full stop every time this happens. Unless users only use the default list views, it is impossible to work efficiently when moving between pages.
This is not a “feature request.” It is fundamental software behavior that has been solved in applications for decades. Any tool with sortable and filterable lists as a core component must persist these settings.
There are multiple well-understood ways to do this, including:
- Persisting settings in the URL so navigation or session reloads maintain state
- Storing preferences in session or local storage
- Saving user-level defaults or remembered views
Why does Jobber not implement one of these basic solutions?
Jobber positions workflow efficiency as a core value. Why are users who rely on sort and filter options condemned to endless repetitive actions? Instead of working on my business, why do I have to spend that time creating scripts that save sort and filter changes and reapply them every time the page loads?
This is a critical UX failure that directly slows daily work for nearly everyone. If this is technical debt, it's too big to keep ignoring at the cost of user experience. When will this be addressed?
