github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 04:02:38 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: Sorting by payee does not sort transfers #1224

New Issue
Open
opened 2026-02-28 19:36:33 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-28 19:36:33 -06:00
Owner
Copy Link

Originally created by @alexandergillon on GitHub (Jul 12, 2024).

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?

Go to any account and sort by Payee column. Transfers will all be lumped together, with no sorting among them.

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 10

Originally created by @alexandergillon on GitHub (Jul 12, 2024). ### 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? Go to any account and sort by Payee column. Transfers will all be lumped together, with no sorting among them. ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 10
GiteaMirror added the user interfacetransactionsgood first issuebug labels 2026-02-28 19:36:33 -06:00
GiteaMirror commented 2026-02-28 19:36:34 -06:00
Author
Owner
Copy Link

@psybers commented on GitHub (Jul 24, 2024):

I can confirm this. One question is if the transfers should all be at the top/bottom, as they are not (but then within that block, sorted) or if they should intermingle with the non-transfer payees?

@psybers commented on GitHub (Jul 24, 2024): I can confirm this. One question is if the transfers should all be at the top/bottom, as they are not (but then within that block, sorted) or if they should intermingle with the non-transfer payees?
GiteaMirror commented 2026-02-28 19:36:34 -06:00
Author
Owner
Copy Link

@Teprifer commented on GitHub (Jul 24, 2024):

I'd pick intermingled based on the other account name.

@Teprifer commented on GitHub (Jul 24, 2024): I'd pick intermingled based on the other account name.
GiteaMirror commented 2026-02-28 19:36:35 -06:00
Author
Owner
Copy Link

@alexandergillon commented on GitHub (Jul 24, 2024):

I can see utility both ways, and I suppose it could be configurable. But if it were one or the other, I would probably agree that they should intermingle.

@alexandergillon commented on GitHub (Jul 24, 2024): I can see utility both ways, and I suppose it could be configurable. But if it were one or the other, I would probably agree that they should intermingle.
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 bug good first issue transactions user interface
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#1224
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?