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

[GH-ISSUE #1039] [Feature] Retain months viewed range #7343

New Issue
Closed
opened 2026-04-10 17:07:36 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-10 17:07:36 -05:00
Owner
Copy Link

Originally created by @youngcw on GitHub (May 16, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1039

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?

When viewing multiple months in the budget window I like to set the view to last/current/next month. Ex. at time of writing I would look at the budgets for April/May/June.

The next time I open the browser window I still can view 3 months, but it starts at the current month instead of remembering the last used range.

Describe your ideal solution to this problem

Save the viewed months in the cached data along with the number of months viewed so a user can jump back in to the same setup as the last time.

Teaching and learning

No response

Originally created by @youngcw on GitHub (May 16, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1039 ### 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? When viewing multiple months in the budget window I like to set the view to last/current/next month. Ex. at time of writing I would look at the budgets for April/May/June. The next time I open the browser window I still can view 3 months, but it starts at the current month instead of remembering the last used range. ### Describe your ideal solution to this problem Save the viewed months in the cached data along with the number of months viewed so a user can jump back in to the same setup as the last time. ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-04-10 17:07:36 -05:00
GiteaMirror commented 2026-04-10 17:07:38 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 16, 2023):

✨ Thanks for sharing your idea! ✨

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 👍!

<!-- gh-comment-id:1550193044 --> @github-actions[bot] commented on GitHub (May 16, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 -->
GiteaMirror commented 2026-04-10 17:07:38 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jul 27, 2023):

Im happy that #1237 got merged in. Would it be doable to retain the viewed range per budget instead of across all budgets? I often jump between main/business/testing budgets and would prefer they each retained their own view range

<!-- gh-comment-id:1653871164 --> @youngcw commented on GitHub (Jul 27, 2023): Im happy that #1237 got merged in. Would it be doable to retain the viewed range per budget instead of across all budgets? I often jump between main/business/testing budgets and would prefer they each retained their own view range
GiteaMirror commented 2026-04-10 17:07:39 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Jul 27, 2023):

I believe they are stored on the local prefs object which should be separate for each budget file.

<!-- gh-comment-id:1654081785 --> @j-f1 commented on GitHub (Jul 27, 2023): I believe they are stored on the local prefs object which should be separate for each budget file.
GiteaMirror commented 2026-04-10 17:07:40 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jul 27, 2023):

Im seeing the view retained between different files. I can set it to something crazy like 6 months starting a year ago, then close the file and open another and get that same view

<!-- gh-comment-id:1654091205 --> @youngcw commented on GitHub (Jul 27, 2023): Im seeing the view retained between different files. I can set it to something crazy like 6 months starting a year ago, then close the file and open another and get that same view
GiteaMirror commented 2026-04-10 17:07:40 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jul 27, 2023):

hmm, I was seeing it sometimes, but now it seems to be gone. Maybe the version I was on before updating didn't have that PR yet.

I am still consistently seeing that the number of viewed months doesn't stay within a single file.

<!-- gh-comment-id:1654175379 --> @youngcw commented on GitHub (Jul 27, 2023): hmm, I was seeing it sometimes, but now it seems to be gone. Maybe the version I was on before updating didn't have that PR yet. I am still consistently seeing that the number of viewed months doesn't stay within a single file.
GiteaMirror commented 2026-04-10 17:07:41 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Jul 27, 2023):

hmm, I was seeing it sometimes, but now it seems to be gone. Maybe the version I was on before updating didn't have that PR yet.

Phew! I checked the code and it looks like the local prefs are always cleared when closing a file, but maybe we missed something since the current open budget state is stored on both the server and client sides in the browser independently.

I am still consistently seeing that the number of viewed months doesn't stay within a single file.

That is intentional since the maxMonths pref is stored in the globalPrefs. I don’t really feel strongly that it needs to be there, though.

<!-- gh-comment-id:1654244023 --> @j-f1 commented on GitHub (Jul 27, 2023): > hmm, I was seeing it sometimes, but now it seems to be gone. Maybe the version I was on before updating didn't have that PR yet. Phew! I checked the code and it looks like the local prefs are always cleared when closing a file, but maybe we missed something since the current open budget state is stored on both the server and client sides in the browser independently. > I am still consistently seeing that the number of viewed months doesn't stay within a single file. That is intentional since the `maxMonths` pref is stored in the globalPrefs. I don’t really feel strongly that it needs to be there, though.
GiteaMirror commented 2026-04-10 17:07:42 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jul 27, 2023):

That is intentional since the maxMonths pref is stored in the globalPrefs. I don’t really feel strongly that it needs to be there, though.

I would be onboard with changing that pref to be per file instead of global.

<!-- gh-comment-id:1654250702 --> @youngcw commented on GitHub (Jul 27, 2023): > That is intentional since the `maxMonths` pref is stored in the globalPrefs. I don’t really feel strongly that it needs to be there, though. I would be onboard with changing that pref to be per file instead of global.
GiteaMirror commented 2026-04-10 17:07:43 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jul 28, 2023):

probably can remove needs votes. Maybe if the number of months being across all files is annoying enough it can get its own feature request.

<!-- gh-comment-id:1656364212 --> @youngcw commented on GitHub (Jul 28, 2023): probably can remove `needs votes`. Maybe if the number of months being across all files is annoying enough it can get its own feature request.
GiteaMirror commented 2026-04-10 17:07:44 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Jul 28, 2023):

Yep! The automation failed 🤦

Hopefully fixing in #1411

<!-- gh-comment-id:1656433879 --> @j-f1 commented on GitHub (Jul 28, 2023): Yep! The [automation](https://github.com/actualbudget/actual/actions/runs/5615144021/job/15214786455) failed 🤦 Hopefully fixing in #1411
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
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#7343
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?