github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-15 22:54:03 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #5188] [Feature] Allow Column Resizing in Transaction View #116592

New Issue
Closed
opened 2026-06-11 10:01:54 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-06-11 10:01:54 -05:00
Owner
Copy Link

Originally created by @cthybert on GitHub (Jun 17, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5188

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?

Currently, column widths in the transaction view are fixed. This presents two main issues:

  1. "Notes" column is too narrow: Notes are often truncated, making it hard to read the full content without clicking into each transaction. This is particularly difficult when categorizing imported transactions where notes are crucial.
  2. "Payee" column is too wide: The payee column often takes up more space than necessary, reducing the available area for other important data like notes.

Describe your ideal solution to this problem

Implement draggable column dividers in the transaction view, allowing users to manually resize columns.

Ideally, these custom widths would be persisted (e.g., via localStorage or user settings) so they remain between sessions.

Benefits:

  • Improved readability of long notes.
  • Faster and more accurate transaction categorization.
  • Better use of screen real estate.
  • More flexible and user-friendly interface.

Teaching and learning

No response

Originally created by @cthybert on GitHub (Jun 17, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5188 ### 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? Currently, column widths in the transaction view are fixed. This presents two main issues: 1. **"Notes" column is too narrow:** Notes are often truncated, making it hard to read the full content without clicking into each transaction. This is particularly difficult when categorizing imported transactions where notes are crucial. 2. **"Payee" column is too wide:** The payee column often takes up more space than necessary, reducing the available area for other important data like notes. ### Describe your ideal solution to this problem Implement draggable column dividers in the transaction view, allowing users to manually resize columns. Ideally, these custom widths would be persisted (e.g., via `localStorage` or user settings) so they remain between sessions. **Benefits:** * Improved readability of long notes. * Faster and more accurate transaction categorization. * Better use of screen real estate. * More flexible and user-friendly interface. ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-06-11 10:01:54 -05:00
GiteaMirror commented 2026-06-11 10:01:55 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 17, 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 👍!

<!-- gh-comment-id:2981954014 --> @github-actions[bot] commented on GitHub (Jun 17, 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 -->
GiteaMirror commented 2026-06-11 10:01:55 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jun 17, 2025):

duplicate #536

<!-- gh-comment-id:2981960644 --> @youngcw commented on GitHub (Jun 17, 2025): duplicate #536
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
tech-support
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#116592
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?