github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-10 16:26:43 -05:00
Code Issues 1.6k Packages Projects Releases 57 Wiki Activity

[Feature] Make the budget timeline fixed width #2313

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

Originally created by @nirvdrum on GitHub (Jul 26, 2025).

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'm working on migrating from Financier to Actual. I've found it easiest to debug issue by focusing on the first month of my budget. Since there's no way to quickly jump to a given month and year (at least that I've found), I'm clicking the "Previous Month" button in the budget timeline until I reach the month I care about. Unfortunately, that button can move around, as can the "Next Month".

The "Previous Month" button moving is particularly problematic, however, because it's right next to the "Today" button. It's quite frustrating navigating back a decade by clicking the "Previous Month" button 100+ times only to have the UI shift and causing me to click the "Today" button, undoing all of my current navigation.

The "Previous Month" button seems to stay fixed if I'm only showing one month at a time, but the "Next Month" button will shift. If I have more than one month displayed, the "Previous Month" button will shift with some regularity.

Describe your ideal solution to this problem

If the budget timeline were a fixed width, then the navigation buttons could be fixed in place as well. I realize the width and positioning will change as the number of months to display changes and that may be fine (although, worth looking into), but I don't think the nav should bounce around when the number of months to display isn't changing.

Teaching and learning

No response

Originally created by @nirvdrum on GitHub (Jul 26, 2025). ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [x] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? I'm working on migrating from Financier to Actual. I've found it easiest to debug issue by focusing on the first month of my budget. Since there's no way to quickly jump to a given month and year (at least that I've found), I'm clicking the "Previous Month" button in the budget timeline until I reach the month I care about. Unfortunately, that button can move around, as can the "Next Month". The "Previous Month" button moving is particularly problematic, however, because it's right next to the "Today" button. It's quite frustrating navigating back a decade by clicking the "Previous Month" button 100+ times only to have the UI shift and causing me to click the "Today" button, undoing all of my current navigation. The "Previous Month" button seems to stay fixed if I'm only showing one month at a time, but the "Next Month" button will shift. If I have more than one month displayed, the "Previous Month" button will shift with some regularity. ### Describe your ideal solution to this problem If the budget timeline were a fixed width, then the navigation buttons could be fixed in place as well. I realize the width and positioning will change as the number of months to display changes and that may be fine (although, worth looking into), but I don't think the nav should bounce around when the number of months to display isn't changing. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 20:10:10 -06:00
GiteaMirror commented 2026-02-28 20:10:11 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 26, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 (Jul 26, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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#2313
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?