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 #2579] [Bug]: Income category group has a hide option #15274

New Issue
Closed
opened 2026-04-14 18:11:43 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-14 18:11:43 -05:00
Owner
Copy Link

Originally created by @jsehnoutka on GitHub (Apr 10, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2579

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

After hiding out the entire income group, nothing visually changes in the GUI (the group name doesn't fade out) nor gives any visual signal to the user.

This can lead to confusion as it effectively disables the ability of adding any income transaction throughout the application in case the "hide" option is selected on the entire Income group unintentionally.

As per Discord discussion this should be probably fixed by removing the "Hide" option on the Income category group.

Category

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @jsehnoutka on GitHub (Apr 10, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2579 ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? After hiding out the entire income group, nothing visually changes in the GUI (the group name doesn't fade out) nor gives any visual signal to the user. This can lead to confusion as it effectively disables the ability of adding any income transaction throughout the application in case the "hide" option is selected on the entire Income group unintentionally. As per Discord discussion this should be probably fixed by removing the "Hide" option on the Income category group. ![Category](https://github.com/actualbudget/actual/assets/133903243/f363da13-eb26-48a9-8a72-b5673de486ed) ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11
GiteaMirror added the bug label 2026-04-14 18:11:43 -05:00
GiteaMirror commented 2026-04-14 18:11:44 -05:00
Author
Owner
Copy Link

@jsehnoutka commented on GitHub (Apr 10, 2024):

also related to #2578

<!-- gh-comment-id:2048286412 --> @jsehnoutka commented on GitHub (Apr 10, 2024): also related to #2578
GiteaMirror commented 2026-04-14 18:11:44 -05:00
Author
Owner
Copy Link

@psybers commented on GitHub (Apr 10, 2024):

This is an easy fix. I have it done locally:

image

But the question is how do we handle migrating existing budget files? Someone might have their income group hidden. With this fix, they would never be able to unhide it...

Can we force the income group to be unhidden on file load or something?

<!-- gh-comment-id:2048288745 --> @psybers commented on GitHub (Apr 10, 2024): This is an easy fix. I have it done locally: <img width="296" alt="image" src="https://github.com/actualbudget/actual/assets/1115390/97d24b5a-e422-44eb-b6c2-8b411ae401ec"> But the question is how do we handle migrating existing budget files? Someone might have their income group hidden. With this fix, they would never be able to unhide it... Can we force the income group to be unhidden on file load or something?
GiteaMirror commented 2026-04-14 18:11:45 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Apr 10, 2024):

Could the db be updated just by running some aql in the browser console? That ability was added recently for these kind of db issues

<!-- gh-comment-id:2048291382 --> @youngcw commented on GitHub (Apr 10, 2024): Could the db be updated just by running some aql in the browser console? That ability was added recently for these kind of db issues
GiteaMirror commented 2026-04-14 18:11:45 -05:00
Author
Owner
Copy Link

@psybers commented on GitHub (Apr 10, 2024):

It could. So you would recommend just making the change and if someone decides later they wanted their income group not hidden they would have to figure out how to run a query to fix it?

<!-- gh-comment-id:2048293660 --> @psybers commented on GitHub (Apr 10, 2024): It could. So you would recommend just making the change and if someone decides later they wanted their income group not hidden they would have to figure out how to run a query to fix it?
GiteaMirror commented 2026-04-14 18:11:45 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Apr 10, 2024):

It could. So you would recommend just making the change and if someone decides later they wanted their income group not hidden they would have to figure out how to run a query to fix it?

Mostly I doubt there are many that have done that, and if it comes up we have a fix ready that is easy enough to share

<!-- gh-comment-id:2048295660 --> @youngcw commented on GitHub (Apr 10, 2024): > It could. So you would recommend just making the change and if someone decides later they wanted their income group not hidden they would have to figure out how to run a query to fix it? Mostly I doubt there are many that have done that, and if it comes up we have a fix ready that is easy enough to share
GiteaMirror commented 2026-04-14 18:11:46 -05:00
Author
Owner
Copy Link

@psybers commented on GitHub (Apr 10, 2024):

@youngcw Actually, does aql allow updates or is it select-only?

<!-- gh-comment-id:2048338357 --> @psybers commented on GitHub (Apr 10, 2024): @youngcw Actually, does aql allow updates or is it select-only?
GiteaMirror commented 2026-04-14 18:11:46 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Apr 10, 2024):

@youngcw Actually, does aql allow updates or is it select-only?

might just be reads without specific functions in the api

<!-- gh-comment-id:2048340715 --> @youngcw commented on GitHub (Apr 10, 2024): > @youngcw Actually, does aql allow updates or is it select-only? might just be reads without specific functions in the api
GiteaMirror commented 2026-04-14 18:11:47 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Apr 10, 2024):

I guess the other good option is to not care about if there hidden flag is set or not so then if someone has it hidden it will just show up going forward. this might already be how it works

<!-- gh-comment-id:2048372573 --> @youngcw commented on GitHub (Apr 10, 2024): I guess the other good option is to not care about if there hidden flag is set or not so then if someone has it hidden it will just show up going forward. this might already be how it works
GiteaMirror commented 2026-04-14 18:11:47 -05:00
Author
Owner
Copy Link

@psybers commented on GitHub (Apr 10, 2024):

I can confirm that! Mine is hidden but still shows.

The problem is the transactions. You won't be able to classify any as an income category if your income group is hidden.

<!-- gh-comment-id:2048376232 --> @psybers commented on GitHub (Apr 10, 2024): I can confirm that! Mine is hidden but still shows. The problem is the transactions. You won't be able to classify any as an income category if your income group is hidden.
GiteaMirror commented 2026-04-14 18:11:48 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Apr 10, 2024):

I can confirm that! Mine is hidden but still shows.

The problem is the transactions. You won't be able to classify any as an income category if your income group is hidden.

Ok. So if the category picker just always includes the income group that seems like the way to fix things

<!-- gh-comment-id:2048382254 --> @youngcw commented on GitHub (Apr 10, 2024): > I can confirm that! Mine is hidden but still shows. > > The problem is the transactions. You won't be able to classify any as an income category if your income group is hidden. Ok. So if the category picker just always includes the income group that seems like the way to fix things
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 bug
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#15274
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?