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

[GH-ISSUE #4366] [Feature] Ability to choose above the break sidebar pages #27646

New Issue
Closed
opened 2026-04-18 04:14:59 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-18 04:14:59 -05:00
Owner
Copy Link

Originally created by @youngcw on GitHub (Feb 12, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4366

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?

The sidebar is currently locked to having "Budget", "Reports", and "Schedules" as full size and everything else is under "more" as a reduced size page. It would be useful for the large icons to be user configurable to better match individual usage of Actual.

Describe your ideal solution to this problem

Allow the user to drag and drop which pages are persistent and which pages are underneath the "more" menu. I don't know if we should still limit to three large pages, or make that adjustable too.

This could also be coupled with the ability to set the default page to something other than budget. Like if a user would rather look at reports on app open than the budget.

Teaching and learning

No response

Originally created by @youngcw on GitHub (Feb 12, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4366 ### 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? The sidebar is currently locked to having "Budget", "Reports", and "Schedules" as full size and everything else is under "more" as a reduced size page. It would be useful for the large icons to be user configurable to better match individual usage of Actual. ### Describe your ideal solution to this problem Allow the user to drag and drop which pages are persistent and which pages are underneath the "more" menu. I don't know if we should still limit to three large pages, or make that adjustable too. This could also be coupled with the ability to set the default page to something other than budget. Like if a user would rather look at reports on app open than the budget. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-04-18 04:14:59 -05:00
GiteaMirror commented 2026-04-18 04:15:00 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 12, 2025):

✨ 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 👍!

<!-- gh-comment-id:2654265605 --> @github-actions[bot] commented on GitHub (Feb 12, 2025): :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#27646
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?