[GH-ISSUE #536] [Feature] Resizable columns #7148

New Issue

GiteaMirror · 2026-04-10T16:50:58-05:00

GiteaMirror commented

2026-04-10 16:50:58 -05:00

Originally created by @rich-howell on GitHub (Jan 22, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/536

Discussed in https://github.com/actualbudget/actual/discussions/172

^{Originally posted by mekkanik June 17, 2022}
Currently when my balances or transaction values run into six digits, they are not showing up in the columns properly. It gets cut off with a '...' Resizable columns would go a long way in alleviating this issue.

Originally created by @rich-howell on GitHub (Jan 22, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/536 ### Discussed in https://github.com/actualbudget/actual/discussions/172 <div type='discussions-op-text'> <sup>Originally posted by **mekkanik** June 17, 2022</sup> Currently when my balances or transaction values run into six digits, they are not showing up in the columns properly. It gets cut off with a '...' Resizable columns would go a long way in alleviating this issue.</div>

GiteaMirror added the good first issue user interface feature needs votes labels 2026-04-10 16:50:59 -05:00

GiteaMirror closed this issue

2026-04-10 16:50:59 -05:00

GiteaMirror commented

2026-04-10 16:51:00 -05:00

@cacti23 commented on GitHub (Feb 5, 2023):

@rich-howell please assign me this issue

@cacti23 commented on GitHub (Feb 5, 2023): @rich-howell please assign me this issue

GiteaMirror commented

2026-04-10 16:51:00 -05:00

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

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

GiteaMirror commented

2026-04-10 16:51:00 -05:00

@bstritesky commented on GitHub (Jun 13, 2023):

Just leaving a comment so it has a few more keywords: resize, wider, width

@bstritesky commented on GitHub (Jun 13, 2023): Just leaving a comment so it has a few more keywords: resize, wider, width

GiteaMirror commented

2026-04-10 16:51:00 -05:00

@danielo515 commented on GitHub (Jul 18, 2024):

I wonder why nobody mentioned the word "tables", that is what I was looking for to upvote 😄

@danielo515 commented on GitHub (Jul 18, 2024): I wonder why nobody mentioned the word "tables", that is what I was looking for to upvote 😄

GiteaMirror commented

2026-04-10 16:51:01 -05:00

@pogman-code commented on GitHub (Dec 12, 2024):

Also having configurable multi-sort by default for transactions would be nice.
Right now all transaction happening on the same day do not seem to have any order, sorting by amount in addition to the date for example would be a nice addition.

@pogman-code commented on GitHub (Dec 12, 2024): Also having configurable multi-sort by default for transactions would be nice. Right now all transaction happening on the same day do not seem to have any order, sorting by amount in addition to the date for example would be a nice addition.

GiteaMirror commented

2026-04-10 16:51:01 -05:00

@sidoshi commented on GitHub (Dec 14, 2024):

I was trying to work on this to get introduced to the codebase.

The balance values only show the ellipsis when there is no more room left on the screen. If we have a 2 month view, the balances are shown fine as there's more room available. Even if we add the feature to resize the columns, some balance will still have to show the ellipsis as there isn't enough room for all the columns to breathe.

Looking at the number of votes on this feature request, I think I am missing something obvious. What is the motivation behind wanting to resize the columns instead of decreasing the visible months to create more space? Is it to have more control over which columns are fully visible and which are hidden while maintaining a higher visible months count?

@sidoshi commented on GitHub (Dec 14, 2024): I was trying to work on this to get introduced to the codebase. The balance values only show the ellipsis when there is no more room left on the screen. If we have a 2 month view, the balances are shown fine as there's more room available. Even if we add the feature to resize the columns, some balance will still have to show the ellipsis as there isn't enough room for all the columns to breathe. Looking at the number of votes on this feature request, I think I am missing something obvious. What is the motivation behind wanting to resize the columns instead of decreasing the visible months to create more space? Is it to have more control over which columns are fully visible and which are hidden while maintaining a higher visible months count? <img width="1435" alt="image" src="https://github.com/user-attachments/assets/4523d5ad-ad6b-435f-8a1f-932edb888e8a" /> <img width="1431" alt="image" src="https://github.com/user-attachments/assets/12e1c4e8-b010-4de4-b7a0-debd9bcb1d4e" />

GiteaMirror commented

2026-04-10 16:51:02 -05:00

@danielo515 commented on GitHub (Dec 14, 2024):

What is the motivation behind wanting to resize the columns instead of decreasing the visible months to create more space?

Some of us are willing to do horizontal scroll. I prefer to be able to see the whole information, even if for that I need to scroll horizontally back and forth. That is still easier than having to move from one month to another

@danielo515 commented on GitHub (Dec 14, 2024): > What is the motivation behind wanting to resize the columns instead of decreasing the visible months to create more space? Some of us are willing to do horizontal scroll. I prefer to be able to see the whole information, even if for that I need to scroll horizontally back and forth. That is still easier than having to move from one month to another

GiteaMirror commented

2026-04-10 16:51:02 -05:00

@bstritesky commented on GitHub (Dec 14, 2024):

What is the motivation behind wanting to resize the columns instead of decreasing the visible months to create more space? Is it to have more control over which columns are fully visible and which are hidden while maintaining a higher visible months count?

I think the budgets area is fine. The transactions views should allow for resizing/reordering of the columns.

@bstritesky commented on GitHub (Dec 14, 2024): > What is the motivation behind wanting to resize the columns instead of decreasing the visible months to create more space? Is it to have more control over which columns are fully visible and which are hidden while maintaining a higher visible months count? I think the budgets area is fine. The transactions views should allow for resizing/reordering of the columns.

GiteaMirror commented

2026-04-10 16:51:02 -05:00

@alcroito commented on GitHub (Dec 14, 2024):

My main use case would be to allow resizing the category names on the budget page, because i have some very long category names, especially when importing hidden category names from ynab4, and it's not possible to distinguish them because each 'subcategory' is prefixed with the main 'category'.

@alcroito commented on GitHub (Dec 14, 2024): My main use case would be to allow resizing the category names on the budget page, because i have some very long category names, especially when importing hidden category names from ynab4, and it's not possible to distinguish them because each 'subcategory' is prefixed with the main 'category'. <img width="1350" alt="Screenshot 2024-12-14 at 16 11 13" src="https://github.com/user-attachments/assets/ebb6ab9d-29ca-44b9-8e38-b62a10a93084" />

GiteaMirror commented

2026-04-10 16:51:03 -05:00

@Gepstra commented on GitHub (Jan 6, 2025):

I was trying to work on this to get introduced to the codebase.

The balance values only show the ellipsis when there is no more room left on the screen. If we have a 2 month view, the balances are shown fine as there's more room available. Even if we add the feature to resize the columns, some balance will still have to show the ellipsis as there isn't enough room for all the columns to breathe.

Looking at the number of votes on this feature request, I think I am missing something obvious. What is the motivation behind wanting to resize the columns instead of decreasing the visible months to create more space? Is it to have more control over which columns are fully visible and which are hidden while maintaining a higher visible months count?

For me this is the main issue:

Category names.

@Gepstra commented on GitHub (Jan 6, 2025): > I was trying to work on this to get introduced to the codebase. > > The balance values only show the ellipsis when there is no more room left on the screen. If we have a 2 month view, the balances are shown fine as there's more room available. Even if we add the feature to resize the columns, some balance will still have to show the ellipsis as there isn't enough room for all the columns to breathe. > > Looking at the number of votes on this feature request, I think I am missing something obvious. What is the motivation behind wanting to resize the columns instead of decreasing the visible months to create more space? Is it to have more control over which columns are fully visible and which are hidden while maintaining a higher visible months count? > For me this is the main issue: ![firefox_K2vrJyVfMx](https://github.com/user-attachments/assets/91d7dc26-6099-4784-adb0-036367a0a54b) Category names.

GiteaMirror commented

2026-04-10 16:51:03 -05:00

@Rick-Thomas commented on GitHub (Feb 6, 2025):

I think the budgets area is fine. The transactions views should allow for resizing/reordering of the columns.

I agree with @bstritesky , but it is not only with the Account Registers where Resizing Columns would be useful, but also in the Schedules, where the amount ends up with "..." and there is a lot of room in Name, Payee and Account...

@Rick-Thomas commented on GitHub (Feb 6, 2025): > I think the budgets area is fine. The transactions views should allow for resizing/reordering of the columns. I agree with @bstritesky , but it is not only with the Account Registers where Resizing Columns would be useful, but also in the Schedules, where the amount ends up with "..." and there is a lot of room in Name, Payee and Account...

GiteaMirror commented

2026-04-10 16:51:04 -05:00

@JonoSK commented on GitHub (Mar 8, 2025):

Why did this get closed? It hasn’t been implemented yet has it?

@JonoSK commented on GitHub (Mar 8, 2025): Why did this get closed? It hasn’t been implemented yet has it?

GiteaMirror commented

2026-04-10 16:51:04 -05:00

@lelemm commented on GitHub (Mar 8, 2025):

Why did this get closed? It hasn’t been implemented yet has it?

All feature request are closed and tagged as "need votes"

@lelemm commented on GitHub (Mar 8, 2025): > Why did this get closed? It hasn’t been implemented yet has it? All feature request are closed and tagged as "need votes"

GiteaMirror commented

2026-04-10 16:51:05 -05:00

@dynek commented on GitHub (Apr 11, 2025):

So we're stuck with fixed size columns?
No https://github.com/actualbudget/actual/pull/3309 and no https://github.com/actualbudget/actual/pull/3445 ?

Let's hope https://github.com/actualbudget/actual/pull/4573 progresses further.

@dynek commented on GitHub (Apr 11, 2025): So we're stuck with fixed size columns? No https://github.com/actualbudget/actual/pull/3309 and no https://github.com/actualbudget/actual/pull/3445 ? Let's hope https://github.com/actualbudget/actual/pull/4573 progresses further.