github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[Feature] Persist view state as user navigates app #1466

New Issue
Closed
opened 2026-02-28 19:44:17 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 19:44:17 -06:00
Owner
Copy Link

Originally created by @mullermn on GitHub (Oct 4, 2024).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

I find that budgeting can often involve a lot of flipping between different views in the app - either different accounts or from the account to the budget screen, etc. At the moment Actual will lose any useful state from the view the user was looking at when they navigate away, making this workflow frustrating.

The ability to save filters exists, but this only covers part of the view state, still requires the user to reapply the filter manually and is not a good workflow for one-off investigations.

Describe your ideal solution to this problem

The app should maintain the state of each account, budget and report view as the user navigates around the app. This includes:
Applied filters
Applied search terms
Scroll bar position
Any selected transactions

Conceptually this is as if each account/report/budget screen was open in a different browser tab and the user was flipping between tabs.

Teaching and learning

I think this is probably the default expectation and doesn't require explanation. I think the current behaviour is less natural and requires the user to learn restraint in their workflow.

Originally created by @mullermn on GitHub (Oct 4, 2024). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? I find that budgeting can often involve a lot of flipping between different views in the app - either different accounts or from the account to the budget screen, etc. At the moment Actual will lose any useful state from the view the user was looking at when they navigate away, making this workflow frustrating. The ability to save filters exists, but this only covers part of the view state, still requires the user to reapply the filter manually and is not a good workflow for one-off investigations. ### Describe your ideal solution to this problem The app should maintain the state of each account, budget and report view as the user navigates around the app. This includes: Applied filters Applied search terms Scroll bar position Any selected transactions Conceptually this is as if each account/report/budget screen was open in a different browser tab and the user was flipping between tabs. ### Teaching and learning I think this is probably the default expectation and doesn't require explanation. I think the current behaviour is less natural and requires the user to learn restraint in their workflow.
GiteaMirror added the featureneeds votes labels 2026-02-28 19:44:17 -06:00
GiteaMirror commented 2026-02-28 19:44:17 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 4, 2024):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Oct 4, 2024): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#1466
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?