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]: Payees should sort favorite payees before other suggested payees. #1367

New Issue
Closed
opened 2026-02-28 19:41:48 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-28 19:41:48 -06:00
Owner
Copy Link

Originally created by @qedi-r on GitHub (Aug 30, 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?

Right now, payees are sorted in three groups, suggested payees, payees and transfers. All are sorted alphabetically. Suggested payees draws from two different sources though, users can either mark payees as favorites, or the most frequently used payees in the past 12 weeks, if users haven't marked at least five payees as favorites.

Since users have specifically marked favorites as desired payees, they should be shown in the suggested payees first. Then common payees should be added. Both subsections should remain otherwise unmarked and be sorted alphabetically.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

No response

Operating System

Windows 11

Originally created by @qedi-r on GitHub (Aug 30, 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? Right now, payees are sorted in three groups, suggested payees, payees and transfers. All are sorted alphabetically. Suggested payees draws from two different sources though, users can either mark payees as favorites, or the most frequently used payees in the past 12 weeks, if users haven't marked at least five payees as favorites. Since users have specifically marked favorites as desired payees, they should be shown in the suggested payees first. Then common payees should be added. Both subsections should remain otherwise unmarked and be sorted alphabetically. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? _No response_ ### Operating System Windows 11
GiteaMirror added the bug label 2026-02-28 19:41:48 -06:00
GiteaMirror commented 2026-02-28 19:41:48 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Sep 9, 2024):

Didn't this get fixed?

@youngcw commented on GitHub (Sep 9, 2024): Didn't this get fixed?
GiteaMirror commented 2026-02-28 19:41:49 -06:00
Author
Owner
Copy Link

@qedi-r commented on GitHub (Sep 9, 2024):

No, I spent too much time figuring out the component test framework. I've created a PR for it now.

@qedi-r commented on GitHub (Sep 9, 2024): No, I spent too much time figuring out the component test framework. I've created a PR for it now.
GiteaMirror commented 2026-02-28 19:41:49 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Sep 9, 2024):

If there is an open PR then you should like it to this issue by adding "fixed #" to the description

@youngcw commented on GitHub (Sep 9, 2024): If there is an open PR then you should like it to this issue by adding "fixed #<this issue>" to the description
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
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#1367
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?