github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-05 22:52:20 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #905] [Bug]: (By design or bug) Clicking "X uncategorized transactions" shows list of transactions in all accounts even if user is in single account view at the moment of click #7291

New Issue
Closed
opened 2026-04-10 17:03:22 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-10 17:03:22 -05:00
Owner
Copy Link

Originally created by @mkalamarz on GitHub (Apr 16, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/905

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

As in title, I'm not sure if this is intended behavior or a bug.

To reproduce:

  1. Have at least 2 accounts with at least 1 uncategorized transaction in each (them being "For budget" shouldn't matter).
  2. Click on one of the accounts, which will show the list of transactions associated with it.
  3. In the top right corner click "X uncategorized transactions".
  4. Even though you were in a specific account view, now you see all the uncategorized transactions (in all accounts)

ALSO in step 2. you can select either a single account or "For budget" or "All accounts".

Weirdly enough in step 4. a completly new type of view (I guess this is called an endpoint?) is forced: accounts/uncategorized. First I thought it simple redirected me to a filtered /accounts.

I would assume this is by design as the number "X" always depicts all uncategorized transactions no matter if a single account or "For budget" or "All accounts" is selected. Also because it always redirects to accounts/uncategorized.

From a UX perspective I would expect to be left in the same "view" and simply get something like a filter "Category is (nothing)" applied to it (it wouldn't work because of #901).

What error did you receive?

No error.

Where are you hosting Actual?

Fly.io

What browsers are you seeing the problem on?

Firefox

Operating System

Windows 10

Originally created by @mkalamarz on GitHub (Apr 16, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/905 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? As in title, I'm not sure if this is intended behavior or a bug. To reproduce: 1. Have at least 2 accounts with at least 1 uncategorized transaction in each (them being "For budget" shouldn't matter). 2. Click on one of the accounts, which will show the list of transactions associated with it. 3. In the top right corner click "X uncategorized transactions". 4. Even though you were in a specific account view, now you see all the uncategorized transactions (in all accounts) ALSO in step 2. you can select either a single account or "For budget" or "All accounts". Weirdly enough in step 4. a completly new type of view (I guess this is called an endpoint?) is forced: **accounts/uncategorized**. First I thought it simple redirected me to a filtered **/accounts**. I would assume this is by design as the number "X" always depicts all uncategorized transactions no matter if a single account or "For budget" or "All accounts" is selected. Also because it always redirects to **accounts/uncategorized**. From a UX perspective I would expect to be left in the same "view" and simply get something like a filter "Category is (nothing)" applied to it (it wouldn't work because of #901). ### What error did you receive? No error. ### Where are you hosting Actual? Fly.io ### What browsers are you seeing the problem on? Firefox ### Operating System Windows 10
GiteaMirror added the wontfix label 2026-04-10 17:03:22 -05:00
GiteaMirror commented 2026-04-10 17:03:24 -05:00
Author
Owner
Copy Link

@mkalamarz commented on GitHub (May 10, 2023):

@j-f1 Bump 🤛 (I know that some issues are more pressing than others but maybe consider adding automation that would ping "someone" or add tag e.x. "stale" when "bug" and "needs triage" are present for more than 2 (?) weeks since posting?)

<!-- gh-comment-id:1542661892 --> @mkalamarz commented on GitHub (May 10, 2023): @j-f1 Bump 🤛 (I know that some issues are more pressing than others but maybe consider adding automation that would ping "someone" or add tag e.x. "stale" when "bug" and "needs triage" are present for more than 2 (?) weeks since posting?)
GiteaMirror commented 2026-04-10 17:03:24 -05:00
Author
Owner
Copy Link

@trevdor commented on GitHub (May 10, 2023):

@mkalamarz 'Tis a busy project. But I gotcha:

The behaviors you describe are all as designed, though I see how it could be confusing. The workflow is for where you want to tidy up ALL the transactions you have yet to categorize in your budget, since that's the only way to be sure your budget reflects current reality.

I'd have to ponder it some more, but at first blush, I think jumping to /accounts/budgeted with a filter instead of a special screen at accounts/uncategorized could be a fabulous enhancement and a good way to highlight our filter capabilities. Essentially, this:

Screenshot 2023-05-10 at 3 19 28 PM

Still, definitely a new feature, not a bug.

<!-- gh-comment-id:1542827810 --> @trevdor commented on GitHub (May 10, 2023): @mkalamarz 'Tis a busy project. But I gotcha: The behaviors you describe are all as designed, though I see how it could be confusing. The workflow is for where you want to tidy up ALL the transactions you have yet to categorize in your budget, since that's the only way to be sure your budget reflects current reality. I'd have to ponder it some more, but at first blush, I think jumping to `/accounts/budgeted` with a filter instead of a special screen at `accounts/uncategorized` could be a fabulous enhancement and a good way to highlight our filter capabilities. Essentially, this: <img width="827" alt="Screenshot 2023-05-10 at 3 19 28 PM" src="https://github.com/actualbudget/actual/assets/5862724/1e16d699-aa1e-496a-89a4-b21e7a8734bd"> Still, definitely a new feature, not a bug.
GiteaMirror commented 2026-04-10 17:03:25 -05:00
Author
Owner
Copy Link

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

<!-- gh-comment-id:1542829720 --> @github-actions[bot] commented on GitHub (May 10, 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 👍! <!-- feature-auto-close-comment -->
GiteaMirror commented 2026-04-10 17:03:25 -05:00
Author
Owner
Copy Link

@mkalamarz commented on GitHub (May 13, 2023):

@trevdor This issue has title and description worded as a bug report, so I have created a proper feature request (#1030). Could you please remove the "needs votes" + "feature" tags and bot message while adding (I guess) "wontfix" for no future confusion?

<!-- gh-comment-id:1546648161 --> @mkalamarz commented on GitHub (May 13, 2023): @trevdor This issue has title and description worded as a bug report, so I have created a proper feature request (#1030). Could you please remove the "needs votes" + "feature" tags and bot message while adding (I guess) "wontfix" for no future confusion?
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 wontfix
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#7291
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?